Re: x configuration on sony vaio
amael wrote: > > okay...it didn't work at first so i installed some more packages and > eventually tried XF86Setup and it basically worked fine (messed up screen > though) so i used my config file instead -- didn't work. so i ran XF86Setup > again, this time trying to more or less reproduce my old config file with > that setup program, and this time i even got a nice screen and a good > resolution. anyway, when i run startx it doesn't work either. the problem is > with X because i get the following output when i run either X or startx: > > var: allowed_users, value: rootonly. > var: nice_value, value: -10. It looks like it is asking you to be logged in as root to startx. You can also do something like the following to capture the output of startx. startx > x.txt 2>&1 Hope this helps, eric :-)
Re: x configuration on sony vaio
amael wrote: > > okay, i just figured this out. if anyone experiences the same problem, make > a symlink /etc/X11/X that points to your xserver (the one you want to use!) > and another symlink /etc/XF86Config that points to /etc/X11/XF86Config > There is a file /etc/X11/Xserver. The first line states the server name like XF86_SVGA. Please check this as you should not have to create a symlink. Your method circumvents the way it is suppose to work in Debian. Hope this helps, Eric :-)
Re: x configuration on sony vaio
"William F. Dowling" wrote: > > Eric Richardson writes: > > amael wrote: > > > > > > okay, i just figured this out. [...] > > There is a file /etc/X11/Xserver. The first line states the server name > > like XF86_SVGA. Please check this as you should not have to create a > > symlink. Your method circumvents the way it is suppose to work in > > Debian. > > Thanks for mentioneing this Eric. I was wondering what the message > amael reported was talking about : " ... rootonly ..." I don't really know about this message - I'm pretty new as well. There is a debian-laptop list as well in case anyone is interested. > This is what > my /etc/X11/Xserver has, maybe useful for amael: > $ cat /etc/X11/Xserver > /etc/X11/X > Console > > The first line in this file is the full pathname of the default X server. > The second line shows who is allowed to run the X server: > RootOnly > Console (anyone whose controlling tty is on the console) > Anybody > > Will > > -- > William F. Dowling > ISI/Thomson Scientific (www.isinet.com) > 215-386-0100 x-1156
Re: x configuration on sony vaio
amael wrote: > > > > okay...it didn't work at first so i installed some more packages and > > > eventually tried XF86Setup and it basically worked fine (messed up > screen > > > though) so i used my config file instead -- didn't work. so i ran > XF86Setup > > > again, this time trying to more or less reproduce my old config file > with > > > that setup program, and this time i even got a nice screen and a good > > > resolution. anyway, when i run startx it doesn't work either. the > problem is > > > with X because i get the following output when i run either X or startx: > > > > > > var: allowed_users, value: rootonly. > > > var: nice_value, value: -10. I did a bit of looking as I had some problems when I install as well. First, when you run XF86Setup you should save the file to /etc/X11/XF86Config. There is a symbolic link from /usr/X11R6/lib/X11/XF86Config to that file. The setup program defaults in the the save dialog to the symlink. Also, you shouldn't have to do weird things like copy files around and such on Debian. The whole dpkg, apt approach is so you don't have to do this. So I would try to undo anything abnormal if you can. BTW, I've been using SuSE and have one box to switch to Debian. The first line of the /etc/X11/XF86Config file should be /usr/X11R6/bin/XF86_ where I assume you should have SVGA for . The rest of the file on my box is as follows Console These are the choices RootOnly Console AnyBody I'm running Gnome so I installed gdm(gnome display manager) as the default on install is xdm and twm for the window manager. I also decided to install icewm to run instead of twm but twm will work. apt-get install gdm later you can install icewm or sawmill or whatever. apt-get install icewm Also nothing worked until I rebooted and I got wierd can't open display messages when gdm was not installed or was not running. Also since I didn't pick the svga server during install, I had to do the following. apt-get install xserver-svga You can also do a dpkg -l to list what is installed. Overall, I think Debian rules -- not released before it's time(at least stable). Hope this helps, Eric :-)
Re: dhcp with pcmcia
Andrew D Dixon wrote: > > Hi All, > I'm trying to configure my laptop to use dhcp and I'm running into some > trouble. > > Formerly it was using a static IP address so I went into /etc/pcmcia and > edited network.opts deleting all of the static stuff and I added: > > DHCP="y" > > Now, when I inster my ethernet card I get two beeps, one high and the second > low (problem). the LED's on the jack indicate that the connection's OK but > ifconfig doesn't show an entry for eth0. > You need pump or dhclient installed to negotiate with the dhcpd where you are getting your address and other network params. ifconfig should show lo.(loopback) Use ifconfig to start the interface. ifconfig eth0 up Hope this helps, Eric :-)
Re: Fujitsu C-Series Lifebook as Debian laptop?
"Randolph S. Kahle" wrote: > > I have a friend that has two Fujitsu C-Series Lifebook > portables with 192Meg RAM. He would like to switch > to Debian Linux. > > Has anyone had success with this model portable? > > Should I wait until 2.4.x kernel is out with Debian to > switch him over? Did you take a look at http://www.linux-laptop.net/ ? It might be helpful, Eric :-)
Re: acer vs fujitsu (ultralights)
"David N. Welton" wrote: > > [ please CC replies to me ] > > Hi folks, I'm finally thinking about getting a laptop, and I thought > I'd ask your opinion... > > For no real motive other than the fact that they came to my attention > through Linux people, I'm considering the following: > > Acer TravelMate 350 > http://www.acer.com/aac/products/notebook/tm350/index.htm > > and > > Fujitsu 4546 > http://www.fujitsupc.com/www/products_notebooks.shtml?products/notebooks/tech_specs/s_series_fall00_ts#3 > > Any thoughts? > > Any good sites to look up laptops for Debian and or GNU/Linux? > Compare laptops in general (computers.com kind of sucks)? check out http://www.linux-laptop.net/ Hope this helps, Eric :-)
How to use touch pad and mouse?
Hi, Can I get the touch pad and the ps2 mouse I'm using both to work? I got the mouse to work with the /dev/psaux and I think the /dev/mouse device worked before with the touch pad but now doesn't work. Can I have two Pointer sections in XF86Config? Currently it looks like this. Section "Pointer" Protocol"PS/2" Device "/dev/psaux" BaudRate1200 Emulate3Timeout 50 EndSection Thanks, Eric :-)
Re: How to use touch pad and mouse?
Eric Richardson wrote: > > Hi, > Can I get the touch pad and the ps2 mouse I'm using both to work? > I have a UMAX 533T which is no longer made but works pretty good. I checked the manual and indeed the touch pad is a ps2 device which explains why it worked fine before I plugged the mouse in and I'll use the emulate3button for pasting as noted in the other thread for use when the ps2 mouse is not plugged in. I haven't checked whether bios supports both but I don't remember a setting for this. I'll take a look at XF86Config as well. I'm currently using stable - what is the first kernel that supports USB as a have that port as well? Thanks for the help. Eric :-)
Re: How to use touch pad and mouse?
Eric Richardson wrote: > > I haven't checked whether bios supports both but I don't remember a > setting for this. Bios doesn't have any settings for supporting both. If the mouse is plugged in the pad doesn't work and if it's unplugged the pad works with no rebooting or anything - interesting.
pcmcia statup order
Hi, More than one person(debain-user) is having problems with the startup sequence with pcmcia. I thought I'd ask here as this list is very familiar with pcmcia. Please read the messages below. It seems that /etc/init.d/networking gets called before /etc/init.d/pcmcia. I searched open and closed bugs for [EMAIL PROTECTED] and could not find anything reported about this. Is this a problem that needs to be looked at for the distribution? It sure makes the out of box experience with Debian a little rough. Eric :-) Eric Richardson wrote: > > "Stephen E. Hargrove" wrote: > > > > On Thu, 5 Apr 2001, Mircea Luca wrote: > > > > > > ammit is.IF you browse /etc/rcS.d you'll see S40networking .So if > > > you start pcmcia at 39(with S39 a symlink to /etc/init.d/pcmcia or > > > wahtever the script name is) in rcS.d you'll be just fine.I don't have > > > my laptop at home so can't tell > > > exactly but that's the idea. > > > rcS.d is executed first,then rc(0-6).d .Actually rc.boot is really the > > > first one but that is deprecated and it shouldn't be used. > > > man init > > > will tell you more about the boot process. > > > > > > > That did the trick. Thanks! > > I have a similar problem running stable using pcmcia and DHCP. I have > the following in relevent files in > > /etc/rcS.d. > S35mountall.sh > S39dns-clean > S40hostname.sh > S40networking > S40pump > > In /etc/rc0.d > S35networking > > In /etc/rc1.d > S20single > > In /etc/rc2.d > S11pcmcia > S14ppp > S20inetd > S50netatalk > > Netatalk fails but pump must keep working as eventually eth0 comes up > but usually after the boot is complete and I have GDM running. > > Should I move dnsclean down towards 35 and insert pcmcia afterwords? If > I move the pcmcia up to rcS.d then do I also need to make sure that the K > scripts make sense as well? > > Thanks, > Eric :-)
Re: PCMCIA Support for 2.2.19 kernel
Walt Mankowski wrote: > > I'm confused as to how to upgrade my laptop (currently running potato > 2.2r3) from kernel 2.2.17 to 2.2.19. Which pcmcia-modules package > should I install? There are four choices: > > pcmcia-modules-2.2.19pre17 > pcmcia-modules-2.2.19pre17-compact > pcmcia-modules-2.2.19pre17-ide > pcmcia-modules-2.2.19pre17-idepci > > That gives me only two choices for a kernel image: > > kernel-image-2.2.19pre17-compact > kernel-image-2.2.19pre17-idepci > > Which of these, if any, should I install? Any idea why there aren't > any pcmcia-modules packages for the released 2.2.19 kernel? I'm not sure what to do so I went ahead and filed a bug report. It doesn't make sense to me. It might just be an oversight as the package is not in the stable archive. I tried to install the pcmcia-modules-2.1.19-2 I found in unstable and it doesn't work. I'm using 2.2.17 until this is resolved or I compile them myself. Eric
Re: 2.2.19 won't run on toshiba sat 470CDT
Othmar Pasteka wrote: > > hi, > > update: when cardmgr is started the kernel kills the interrupt > handler ... but still no clue why :(. > > so long > Othmar > > On Thu, May 03, 2001 at 10:03:34AM +0200, Othmar Pasteka wrote: > > i just wanted to upgrade the kernel but all i get with the .19 > > kernel with noting special in it, not even apm stuff, i get a > > "interrupt handler killed" msg during boot time. i can't exactly > > determine when t his happens whether it's during mounting / or > > during rcS.d is run ... > > any hints/suggenstions? I don't have a Toshiba but I'm curious how you got the pcmcia-modules for 2.2.19? I upgraded to 2.2.19 kernel and no pcmcia modules came with the kernel. I filed a bug report and a few days later after I saw the 2.2.19 modules I did an apt-get install pcmcia-modules-2.2.19 and got version 3.1.22-0.2potatok4 and the apt system also replace my kernel with a matching one. This one works. Hope this helps, Eric
Re: 2.2.19 won't run on toshiba sat 470CDT
Othmar Pasteka wrote: > > hi, > > On Thu, May 03, 2001 at 10:39:50AM -0700, Eric Richardson wrote: > > I don't have a Toshiba but I'm curious how you got the pcmcia-modules > > for 2.2.19? I upgraded to 2.2.19 kernel and no pcmcia modules came with > > the kernel. I filed a bug report and a few days later after I saw the > > 2.2.19 modules I did an apt-get install pcmcia-modules-2.2.19 and got > > version 3.1.22-0.2potatok4 and the apt system also replace my kernel > > with a matching one. This one works. > > apt-get source pcmcia-cs and follow the README in debian/, i.e. > do a debian/rules binary-modules ... it needs the linux source in > /usr/src/linux and it also has to be configured ... I did compile the pcmcia-modules but I don't compile my own kernel yet so I couldn't try it out. I don't think you mentioned that you were compiling you own stuff. I thought you were using stock 2.2r3. Eric
USB Problems
Hi, I'm not able to get USB to work so would appreciate some help. I'm using 2.2.19(not a custom build), 2.2r3 stable/proposed updates on a UMAX 533T. I'm trying to use a Belkin USB mouse for starters. Here what I did so far. I used the procedures from the docs on linux-usb.org. 1. loaded the modules - usb-ohci didn't work so I assume the usb-uhci is correct as supported in the boot message below # lsmod (edited) mousedev3596 0 (unused) hid11384 0 (unused) input 2684 0 [mousedev hid] usb-uhci 18200 0 (unused) usbcore41028 0 [hid usb-uhci] 2. added the device files $ ls -la /dev/input total 0 crw---1 root root 13, 63 May 8 09:27 mice crw---1 root root 13, 32 May 8 09:27 mouse0 Note the following. # cat /dev/input/mouse0 cat: /dev/input/mouse0: No such device 3. added to /etc/fstab after /proc entry none /proc/bus/usb usbdevfs defaults 0 0 $ ls /proc/bus/usb 001 devices drivers Results from dmesg usb.c: registered new driver usbdevfs usb.c: registered new driver hub usb-uhci.c: $Revision: 1.237 $ time 22:44:21 Apr 19 2001 usb-uhci.c: High bandwidth mode enabled usb-uhci.c: USB UHCI at I/O 0xf300, IRQ 10 usb-uhci.c: Detected 2 ports usb.c: new USB bus registered, assigned bus number 1 usb.c: USB new device connect, assigned device number 1 hub.c: USB hub found hub.c: 2 ports detected usb.c: registered new driver hid mice: PS/2 mouse device common for all mice usb.c: USB new device connect, assigned device number 2 usb_control/bulk_msg: timeout usb.c: USB device not accepting new address (error=-110) usb.c: USB new device connect, assigned device number -1 usb_control/bulk_msg: timeout usb.c: USB device not accepting new address (error=-110) usb.c: USB disconnect on device -1 $ cat /proc/bus/usb/drivers hid hub usbdevfs $ cat /proc/bus/usb/devices T: Bus=01 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=12 MxCh= 2 B: Alloc= 0/900 us ( 0%), #Int= 0, #Iso= 0 D: Ver= 1.00 Cls=09(hub ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1 P: Vendor= ProdID= Rev= 0.00 S: Product=USB UHCI Root Hub S: SerialNumber=f300 C:* #Ifs= 1 Cfg#= 1 Atr=40 MxPwr= 0mA I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub E: Ad=81(I) Atr=03(Int.) MxPS= 8 Ivl=255ms The only thing weird on the boot mesg is that I physically only have one USB port but the system is trying to assign 2 devices. Thanks in advance for any help. Eric
Update: Re: PCMCIA Support for 2.2.19 kernel
Eric Richardson wrote: > > Walt Mankowski wrote: > > > > I'm confused as to how to upgrade my laptop (currently running potato > > 2.2r3) from kernel 2.2.17 to 2.2.19. Which pcmcia-modules package > > should I install? There are four choices: > > > > pcmcia-modules-2.2.19pre17 > > pcmcia-modules-2.2.19pre17-compact > > pcmcia-modules-2.2.19pre17-ide > > pcmcia-modules-2.2.19pre17-idepci > > > > That gives me only two choices for a kernel image: > > > > kernel-image-2.2.19pre17-compact > > kernel-image-2.2.19pre17-idepci > > > > Which of these, if any, should I install? Any idea why there aren't > > any pcmcia-modules packages for the released 2.2.19 kernel? > > I'm not sure what to do so I went ahead and filed a bug report. It > doesn't make > sense to me. It might just be an oversight as the package is not in the > stable archive. I tried to install the pcmcia-modules-2.1.19-2 > I found in unstable and it doesn't work. I'm using 2.2.17 until this is > resolved or I compile them myself. I added the following to /etc/apt/sources.list # proposed deb http://http.us.debian.org/debian dists/potato-proposed-updates/ deb http://non-us.debian.org/debian-non-US dists/potato-proposed-updates/ apt-get install pcmcia-modules-2.2.19 The updated the modules and added pcmcia and also updated the 2.2.19 kernel to one that matches the compiled modules. I've been using this for a while without any trouble that I'm aware of. Eric
Need PCMCIA help.
Hi, Both my ethernet Controller and the cardbus are using the same interrupt and I'm told this is suboptimal as it is sharing it with USB. PCMCIA is working but USB is not(2.2.19 kernel). How can I update /etc/pcmcia.conf to remedy this? Here is the USB and the PCMCIA dmesg output. The first part of the message prints out options: [pci] [cardbus] [apm] Should this be set to something as well? Thanks for help, Eric usb-uhci.c: USB UHCI at I/O 0xf300, IRQ 10 Linux PCMCIA Card Services 3.1.22 kernel build: 2.2.19 #1 Thu Apr 19 22:35:28 EST 2001 options: [pci] [cardbus] [apm] PCI routing table version 1.0 at 0xfe840 Intel PCIC probe: TI 1225 rev 01 PCI-to-CardBus at slot 00:0a, mem 0x6800 host opts [0]: [serial pci & irq] [pci irq 10] [lat 168/176] [bus 32/34] host opts [1]: [serial pci & irq] [pci irq 10] [lat 168/176] [bus 35/37] ISA irqs (scanned) = 3,4,7,9,11 PCI status changes cs: IO port probe 0x0c00-0x0cff: excluding 0xcf8-0xcff cs: IO port probe 0x0800-0x08ff: excluding 0x800-0x807 cs: IO port probe 0x0100-0x04ff: excluding 0x300-0x307 0x378-0x37f 0x388-0x38f 0x3e8-0x3ff 0x4d0-0x4d7 cs: IO port probe 0x0a00-0x0aff: clean. cs: cb_alloc(bus 35): vendor 0x1011, device 0x0019 ROM image dump: image 0: 0x00-0x0001ff, signature PCIR cs: cb_config(bus 35) fn 0 bar 1: io 0x400-0x47f fn 0 bar 2: mem 0x600c-0x600c007f fn 0 rom: mem 0x6008-0x600b irq 10 cs: cb_enable(bus 35) bridge io map 0 (flags 0x21): 0x400-0x47f bridge mem map 0 (flags 0x1): 0x6008-0x600c0fff tulip_attach(device 23:00.0) tulip.c:v0.91g-ppc 7/16/99 [EMAIL PROTECTED] (modified by [EMAIL PROTECTED] for XIRCOM CBE, fixed by Doug Ledford) eth0: Digital DS21143 Tulip rev 48 at 0x400, 00:10:7A:10:E1:DB, IRQ 10. eth0: EEPROM default media type Autosense. eth0: Index #0 - Media 10baseT (#0) described by a 21142 Serial PHY (2) block. eth0: Index #1 - Media 10baseT-FD (#4) described by a 21142 Serial PHY (2) block. eth0: Index #2 - Media 100baseTx (#3) described by a 21143 SYM PHY (4) block.eth0: Index #3 - Media 100baseTx-FD (#5) described by a 21143 SYM PHY (4) block. cs: memory probe 0xa000-0xa0ff: clean. tty04 at 0x0ae8 (irq = 3) is a 16550A
Re: Need PCMCIA help.
Petr Hlustik wrote: > > Eric, > > > Both my ethernet Controller and the cardbus are using the same interrupt > > and I'm told this is suboptimal as it is sharing it with USB. PCMCIA is > > working but USB is not(2.2.19 kernel). > > [...] > > > Linux PCMCIA Card Services 3.1.22 > > I do not use USB but debian-proposed-updates also has pcmcia-modules > version 2.1.25, which is the one I tried. Maybe the newer PCMCIA modules > got smarter about sharing the IRQs? I've got proposed in my sources. # apt-get install pcmcia-cs Reading Package Lists... Done Building Dependency Tree... Done Sorry, pcmcia-cs is already the newest version 0 packages upgraded, 0 newly installed, 0 to remove and 1 not upgraded. I already have pcmcia-modules-2.2.19 so I'm not sure what you are refering to. Eric
Re: Need PCMCIA help.
Petr Hlustik wrote: > > On Thu, May 10, 2001 at 04:29:54PM -0700, Eric Richardson wrote: > > > > I do not use USB but debian-proposed-updates also has pcmcia-modules > > > version 2.1.25, which is the one I tried. Maybe the newer PCMCIA modules > > > got smarter about sharing the IRQs? > > > > I've got proposed in my sources. > > > > # apt-get install pcmcia-cs > > Reading Package Lists... Done > > Building Dependency Tree... Done > > Sorry, pcmcia-cs is already the newest version > > 0 packages upgraded, 0 newly installed, 0 to remove and 1 not upgraded. > > > > I already have pcmcia-modules-2.2.19 so I'm not sure what you are > > refering to. > > To be honest, I did not use apt, I FPTed to > ftp://ftp.debian.org/debian/pool/main/p/pcmcia-cs/ > > which has these guys: > > pcmcia-modules-2.2.19_3.1.25-3k2_i386.deb > pcmcia-modules-2.2.19_3.1.22-0.2potatok4_i386.deb > > I used the top one... > It looks like the 2.2r4 will have the pcmcia added according to the post PCMCIA Support for 2.2.19 kernel Maybe this will help, eric p.s. I'm learning to compile and install custom kernels since alot of people suggest this is the way to go.
Re: compiling pcmcia-source
Robert Voigt wrote: > > On Thursday 17 May 2001 20:59, Vivek Dasmohapatra wrote: > > I usually use > > > > apt-get install FOO-source > > cd /usr/src/linux > > make-kpkg modules_image > > > > to create the pcmcia/thinkpad/alsa/whatever debs. Have you tried that? > > It says > make-kpkg No such file or directory. > In what package is it? I thought I used it before, don't know what's wrong. It's in kernel-package and here is a good doc that may help. http://newbiedoc.sourceforge.net/system/kernel-pkg.en.html Hope this helps, Eric
How to get libgnome 1.2.x for development?
Hi, I'm on stable and trying to compile a program that requires the following: libgnome 1.2.x, gtk+ 1.2.7 and libxml 1.8.x and gnome-print 0.25. I installed the libgnome-dev (which installs libgtk1.2-dev) and libxml-dev which gives me the following: libgnome 1.0.56, gtk+ 1.2.7 and libxml 1.8.x and gnome-print 0.10. I think the gnome-print comes with libgnome. Anyway, I was wondering how I can get the 1.2 libgnome. It looks like it is libgnome32 in testing but I couldn't find any installable packages. Could I put a deb src for testing and then get the source to compile and then install? What package? Will installing the new libs conflict or mess up the current libs? I really don't want to mess up a perfectly good system because I don't know what I am doing. Any help would be appreciated. Eric
Re: How to get libgnome 1.2.x for development?
Gabor Zoltan Csejtey wrote: > > HI, > > When you download a debian source package after extracting it you can > find the dependencies in the package-version/debian/control file. I couldn't find this but found a debian directory with all the stuff to make a .deb > > There can be more packages to install or compile again. > > e.g I have the following src URI-s in my /etc/apt/sources.list: > #Sources testing > deb-src ftp://sunsite.uio.no/debian testing main non-free contrib > deb-src ftp://sunsite.uio.no/debian-non-US testing/non-US main non-free > contrib Okay, I added these for testing/woody in addition to stable. apt-get source libgnome-dev This gave me version 1.2.13-4 which is good. It wouldn't build. apt-get install xpm4g-dev It is built finally.(It's big) > > You may need: > dpkg-dev - Package building tools for Debian What do I do now? Do I package it some how so I can install it? Of course it has a make install target. Use a ./configure --prefix=PATH and install it via make install somewhere else? When you don't know a process - it stinks. Maybe you know of some documentation for Debian development. Anyway, thank a ton for getting me this far. Eric
Re: libgnome-dev 1.2.x - doesn't compile
Gabor Zoltan Csejtey wrote: > > Hi, > > You can compile the debian source with apt with > > apt-get source -b package_name > > or after getting the source you can use: > > dpkg-buildpackage -uc -b > > in the source directory (the source extracted and patched after > downloading). > this command is called by apt-get if you use the -b option. > If you have troubles compiling the source look at the > debian/rules file in your source directory. > There're the commands for compiling the source package. > > After compiling the package source you'll get xxx.deb installable > packages in the directory which contains the source directory. > (i.e. one level up in the directory hiearchy.) Okay, I tried this and it failed. The follow directories are the trouble maker. gnome-libs-1.2.13/intl gnome-libs-1.2.13/gnome-faq These have no Makefile.in so a empty Makefile gets created which fails on the recursive build. Making clean in intl make[2]: Entering directory `/root/gnome-libs-1.2.13/intl' make[2]: *** No rule to make target `clean'. Stop. make[2]: Leaving directory `/root/gnome-libs-1.2.13/intl' make[1]: *** [clean-recursive] Error 1 make[1]: Leaving directory `/root/gnome-libs-1.2.13' make: *** [clean] Error 2 One other thing. I do not have a deb-src to unstable because I thought it might have even a newer version than 1.2.13 and 1.2 is fine.
Re: libgnome-dev 1.2.x - doesn't compile
Gabor Zoltan Csejtey wrote: > > Hi, > > I downloaded both gnome-libs_1.2.13-6 and gnome-libs_1.2.13-4 sources > from the debian distribution. The location is: > > ftp://ftp.no.debian.org/debian/pool/main/g/gnome-libs/ > > As I see there's a Makefile.in in the > > gnome-libs-1.2.13/intl > > but I couldn't find gnome-libs-1.2.13/gnome-faq directory. > > I tried configure in the gnome-libs-1.2.13 and this made the Makefiles > in gnome-libs-1.2.13/intl too. > > -rw-r--r--1 root root 6514 May 30 12:39 intl/Makefile > -rw-r--r--1 500 500 6455 Mar 16 20:46 intl/Makefile.in > > Gabor > PS. > The source tarball is the same for testing and unstable. The patches > differ: > -rw-r--r--1 csg csg 95498 May 30 12:30 > gnome-libs_1.2.13-4.diff.gz > -rw-r--r--1 root root 178896 May 15 16:27 > gnome-libs_1.2.13-6.diff.gz I'll add the unstable to sources.list - maybe the makefile is in the unstable diff. Is this just coincidence as I thought testing and unstable used different versions of almost everything? Eric
Re: libgnome-dev 1.2.x - doesn't compile
Gabor Zoltan Csejtey wrote: > > Hi, > > I downloaded both gnome-libs_1.2.13-6 and gnome-libs_1.2.13-4 sources > from the debian distribution. The location is: > > ftp://ftp.no.debian.org/debian/pool/main/g/gnome-libs/ > > As I see there's a Makefile.in in the > > gnome-libs-1.2.13/intl > > but I couldn't find gnome-libs-1.2.13/gnome-faq directory. > > I tried configure in the gnome-libs-1.2.13 and this made the Makefiles > in gnome-libs-1.2.13/intl too. > > -rw-r--r--1 root root 6514 May 30 12:39 intl/Makefile > -rw-r--r--1 500 500 6455 Mar 16 20:46 intl/Makefile.in > > Gabor > PS. > The source tarball is the same for testing and unstable. The patches > differ: > -rw-r--r--1 csg csg 95498 May 30 12:30 > gnome-libs_1.2.13-4.diff.gz > -rw-r--r--1 root root 178896 May 15 16:27 > gnome-libs_1.2.13-6.diff.gz Sorry, but do I have to manually apply the diff? Eric
Re: power button dell inspiron 4000
Tim Connors wrote: > > One annoying um, feature, of the dell laptop, is the ability to shut down > immediately upon pressing the power button. I have not found anything on > the web to disable the power button (seems there are lots of references to > toshiba laptops though), has anyone else found anything useful? > > Unfortuneatly, there is nothing in the bios that says "power > switch==off/suspend" - is there a newer bios that fixes this? > If dmesg pumps out something like this, then APM is enabled in the kernel. apm: BIOS version 1.2 Flags 0x03 (Driver version 1.13) Edit /etc/lilo.conf image=/vmlinuz label=Linux read-only append="apm=on" # restricted # alias=1 Add the append line. Then when you halt, APM will shutoff the machine. Hope this helps, Eric
Re: x configuration on sony vaio
amael wrote: > > okay...it didn't work at first so i installed some more packages and > eventually tried XF86Setup and it basically worked fine (messed up screen > though) so i used my config file instead -- didn't work. so i ran XF86Setup > again, this time trying to more or less reproduce my old config file with > that setup program, and this time i even got a nice screen and a good > resolution. anyway, when i run startx it doesn't work either. the problem is > with X because i get the following output when i run either X or startx: > > var: allowed_users, value: rootonly. > var: nice_value, value: -10. It looks like it is asking you to be logged in as root to startx. You can also do something like the following to capture the output of startx. startx > x.txt 2>&1 Hope this helps, eric :-) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: x configuration on sony vaio
amael wrote: > > okay, i just figured this out. if anyone experiences the same problem, make > a symlink /etc/X11/X that points to your xserver (the one you want to use!) > and another symlink /etc/XF86Config that points to /etc/X11/XF86Config > There is a file /etc/X11/Xserver. The first line states the server name like XF86_SVGA. Please check this as you should not have to create a symlink. Your method circumvents the way it is suppose to work in Debian. Hope this helps, Eric :-) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: x configuration on sony vaio
"William F. Dowling" wrote: > > Eric Richardson writes: > > amael wrote: > > > > > > okay, i just figured this out. [...] > > There is a file /etc/X11/Xserver. The first line states the server name > > like XF86_SVGA. Please check this as you should not have to create a > > symlink. Your method circumvents the way it is suppose to work in > > Debian. > > Thanks for mentioneing this Eric. I was wondering what the message > amael reported was talking about : " ... rootonly ..." I don't really know about this message - I'm pretty new as well. There is a debian-laptop list as well in case anyone is interested. > This is what > my /etc/X11/Xserver has, maybe useful for amael: > $ cat /etc/X11/Xserver > /etc/X11/X > Console > > The first line in this file is the full pathname of the default X server. > The second line shows who is allowed to run the X server: > RootOnly > Console (anyone whose controlling tty is on the console) > Anybody > > Will > > -- > William F. Dowling > ISI/Thomson Scientific (www.isinet.com) > 215-386-0100 x-1156 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: x configuration on sony vaio
amael wrote: > > > > okay...it didn't work at first so i installed some more packages and > > > eventually tried XF86Setup and it basically worked fine (messed up > screen > > > though) so i used my config file instead -- didn't work. so i ran > XF86Setup > > > again, this time trying to more or less reproduce my old config file > with > > > that setup program, and this time i even got a nice screen and a good > > > resolution. anyway, when i run startx it doesn't work either. the > problem is > > > with X because i get the following output when i run either X or startx: > > > > > > var: allowed_users, value: rootonly. > > > var: nice_value, value: -10. I did a bit of looking as I had some problems when I install as well. First, when you run XF86Setup you should save the file to /etc/X11/XF86Config. There is a symbolic link from /usr/X11R6/lib/X11/XF86Config to that file. The setup program defaults in the the save dialog to the symlink. Also, you shouldn't have to do weird things like copy files around and such on Debian. The whole dpkg, apt approach is so you don't have to do this. So I would try to undo anything abnormal if you can. BTW, I've been using SuSE and have one box to switch to Debian. The first line of the /etc/X11/XF86Config file should be /usr/X11R6/bin/XF86_ where I assume you should have SVGA for . The rest of the file on my box is as follows Console These are the choices RootOnly Console AnyBody I'm running Gnome so I installed gdm(gnome display manager) as the default on install is xdm and twm for the window manager. I also decided to install icewm to run instead of twm but twm will work. apt-get install gdm later you can install icewm or sawmill or whatever. apt-get install icewm Also nothing worked until I rebooted and I got wierd can't open display messages when gdm was not installed or was not running. Also since I didn't pick the svga server during install, I had to do the following. apt-get install xserver-svga You can also do a dpkg -l to list what is installed. Overall, I think Debian rules -- not released before it's time(at least stable). Hope this helps, Eric :-) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: dhcp with pcmcia
Andrew D Dixon wrote: > > Hi All, > I'm trying to configure my laptop to use dhcp and I'm running into some > trouble. > > Formerly it was using a static IP address so I went into /etc/pcmcia and > edited network.opts deleting all of the static stuff and I added: > > DHCP="y" > > Now, when I inster my ethernet card I get two beeps, one high and the second > low (problem). the LED's on the jack indicate that the connection's OK but > ifconfig doesn't show an entry for eth0. > You need pump or dhclient installed to negotiate with the dhcpd where you are getting your address and other network params. ifconfig should show lo.(loopback) Use ifconfig to start the interface. ifconfig eth0 up Hope this helps, Eric :-) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Fujitsu C-Series Lifebook as Debian laptop?
"Randolph S. Kahle" wrote: > > I have a friend that has two Fujitsu C-Series Lifebook > portables with 192Meg RAM. He would like to switch > to Debian Linux. > > Has anyone had success with this model portable? > > Should I wait until 2.4.x kernel is out with Debian to > switch him over? Did you take a look at http://www.linux-laptop.net/ ? It might be helpful, Eric :-) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: acer vs fujitsu (ultralights)
"David N. Welton" wrote: > > [ please CC replies to me ] > > Hi folks, I'm finally thinking about getting a laptop, and I thought > I'd ask your opinion... > > For no real motive other than the fact that they came to my attention > through Linux people, I'm considering the following: > > Acer TravelMate 350 > http://www.acer.com/aac/products/notebook/tm350/index.htm > > and > > Fujitsu 4546 > >http://www.fujitsupc.com/www/products_notebooks.shtml?products/notebooks/tech_specs/s_series_fall00_ts#3 > > Any thoughts? > > Any good sites to look up laptops for Debian and or GNU/Linux? > Compare laptops in general (computers.com kind of sucks)? check out http://www.linux-laptop.net/ Hope this helps, Eric :-) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
How to use touch pad and mouse?
Hi, Can I get the touch pad and the ps2 mouse I'm using both to work? I got the mouse to work with the /dev/psaux and I think the /dev/mouse device worked before with the touch pad but now doesn't work. Can I have two Pointer sections in XF86Config? Currently it looks like this. Section "Pointer" Protocol"PS/2" Device "/dev/psaux" BaudRate1200 Emulate3Timeout 50 EndSection Thanks, Eric :-) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: How to use touch pad and mouse?
Eric Richardson wrote: > > Hi, > Can I get the touch pad and the ps2 mouse I'm using both to work? > I have a UMAX 533T which is no longer made but works pretty good. I checked the manual and indeed the touch pad is a ps2 device which explains why it worked fine before I plugged the mouse in and I'll use the emulate3button for pasting as noted in the other thread for use when the ps2 mouse is not plugged in. I haven't checked whether bios supports both but I don't remember a setting for this. I'll take a look at XF86Config as well. I'm currently using stable - what is the first kernel that supports USB as a have that port as well? Thanks for the help. Eric :-) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: How to use touch pad and mouse?
Eric Richardson wrote: > > I haven't checked whether bios supports both but I don't remember a > setting for this. Bios doesn't have any settings for supporting both. If the mouse is plugged in the pad doesn't work and if it's unplugged the pad works with no rebooting or anything - interesting. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
pcmcia statup order
Hi, More than one person(debain-user) is having problems with the startup sequence with pcmcia. I thought I'd ask here as this list is very familiar with pcmcia. Please read the messages below. It seems that /etc/init.d/networking gets called before /etc/init.d/pcmcia. I searched open and closed bugs for [EMAIL PROTECTED] and could not find anything reported about this. Is this a problem that needs to be looked at for the distribution? It sure makes the out of box experience with Debian a little rough. Eric :-) Eric Richardson wrote: > > "Stephen E. Hargrove" wrote: > > > > On Thu, 5 Apr 2001, Mircea Luca wrote: > > > > > > ammit is.IF you browse /etc/rcS.d you'll see S40networking .So if > > > you start pcmcia at 39(with S39 a symlink to /etc/init.d/pcmcia or > > > wahtever the script name is) in rcS.d you'll be just fine.I don't have > > > my laptop at home so can't tell > > > exactly but that's the idea. > > > rcS.d is executed first,then rc(0-6).d .Actually rc.boot is really the > > > first one but that is deprecated and it shouldn't be used. > > > man init > > > will tell you more about the boot process. > > > > > > > That did the trick. Thanks! > > I have a similar problem running stable using pcmcia and DHCP. I have > the following in relevent files in > > /etc/rcS.d. > S35mountall.sh > S39dns-clean > S40hostname.sh > S40networking > S40pump > > In /etc/rc0.d > S35networking > > In /etc/rc1.d > S20single > > In /etc/rc2.d > S11pcmcia > S14ppp > S20inetd > S50netatalk > > Netatalk fails but pump must keep working as eventually eth0 comes up > but usually after the boot is complete and I have GDM running. > > Should I move dnsclean down towards 35 and insert pcmcia afterwords? If > I move the pcmcia up to rcS.d then do I also need to make sure that the K > scripts make sense as well? > > Thanks, > Eric :-) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: PCMCIA Support for 2.2.19 kernel
Walt Mankowski wrote: > > I'm confused as to how to upgrade my laptop (currently running potato > 2.2r3) from kernel 2.2.17 to 2.2.19. Which pcmcia-modules package > should I install? There are four choices: > > pcmcia-modules-2.2.19pre17 > pcmcia-modules-2.2.19pre17-compact > pcmcia-modules-2.2.19pre17-ide > pcmcia-modules-2.2.19pre17-idepci > > That gives me only two choices for a kernel image: > > kernel-image-2.2.19pre17-compact > kernel-image-2.2.19pre17-idepci > > Which of these, if any, should I install? Any idea why there aren't > any pcmcia-modules packages for the released 2.2.19 kernel? I'm not sure what to do so I went ahead and filed a bug report. It doesn't make sense to me. It might just be an oversight as the package is not in the stable archive. I tried to install the pcmcia-modules-2.1.19-2 I found in unstable and it doesn't work. I'm using 2.2.17 until this is resolved or I compile them myself. Eric -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: 2.2.19 won't run on toshiba sat 470CDT
Othmar Pasteka wrote: > > hi, > > update: when cardmgr is started the kernel kills the interrupt > handler ... but still no clue why :(. > > so long > Othmar > > On Thu, May 03, 2001 at 10:03:34AM +0200, Othmar Pasteka wrote: > > i just wanted to upgrade the kernel but all i get with the .19 > > kernel with noting special in it, not even apm stuff, i get a > > "interrupt handler killed" msg during boot time. i can't exactly > > determine when t his happens whether it's during mounting / or > > during rcS.d is run ... > > any hints/suggenstions? I don't have a Toshiba but I'm curious how you got the pcmcia-modules for 2.2.19? I upgraded to 2.2.19 kernel and no pcmcia modules came with the kernel. I filed a bug report and a few days later after I saw the 2.2.19 modules I did an apt-get install pcmcia-modules-2.2.19 and got version 3.1.22-0.2potatok4 and the apt system also replace my kernel with a matching one. This one works. Hope this helps, Eric -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: 2.2.19 won't run on toshiba sat 470CDT
Othmar Pasteka wrote: > > hi, > > On Thu, May 03, 2001 at 10:39:50AM -0700, Eric Richardson wrote: > > I don't have a Toshiba but I'm curious how you got the pcmcia-modules > > for 2.2.19? I upgraded to 2.2.19 kernel and no pcmcia modules came with > > the kernel. I filed a bug report and a few days later after I saw the > > 2.2.19 modules I did an apt-get install pcmcia-modules-2.2.19 and got > > version 3.1.22-0.2potatok4 and the apt system also replace my kernel > > with a matching one. This one works. > > apt-get source pcmcia-cs and follow the README in debian/, i.e. > do a debian/rules binary-modules ... it needs the linux source in > /usr/src/linux and it also has to be configured ... I did compile the pcmcia-modules but I don't compile my own kernel yet so I couldn't try it out. I don't think you mentioned that you were compiling you own stuff. I thought you were using stock 2.2r3. Eric -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
USB Problems
Hi, I'm not able to get USB to work so would appreciate some help. I'm using 2.2.19(not a custom build), 2.2r3 stable/proposed updates on a UMAX 533T. I'm trying to use a Belkin USB mouse for starters. Here what I did so far. I used the procedures from the docs on linux-usb.org. 1. loaded the modules - usb-ohci didn't work so I assume the usb-uhci is correct as supported in the boot message below # lsmod (edited) mousedev3596 0 (unused) hid11384 0 (unused) input 2684 0 [mousedev hid] usb-uhci 18200 0 (unused) usbcore41028 0 [hid usb-uhci] 2. added the device files $ ls -la /dev/input total 0 crw---1 root root 13, 63 May 8 09:27 mice crw---1 root root 13, 32 May 8 09:27 mouse0 Note the following. # cat /dev/input/mouse0 cat: /dev/input/mouse0: No such device 3. added to /etc/fstab after /proc entry none /proc/bus/usb usbdevfs defaults 0 0 $ ls /proc/bus/usb 001 devices drivers Results from dmesg usb.c: registered new driver usbdevfs usb.c: registered new driver hub usb-uhci.c: $Revision: 1.237 $ time 22:44:21 Apr 19 2001 usb-uhci.c: High bandwidth mode enabled usb-uhci.c: USB UHCI at I/O 0xf300, IRQ 10 usb-uhci.c: Detected 2 ports usb.c: new USB bus registered, assigned bus number 1 usb.c: USB new device connect, assigned device number 1 hub.c: USB hub found hub.c: 2 ports detected usb.c: registered new driver hid mice: PS/2 mouse device common for all mice usb.c: USB new device connect, assigned device number 2 usb_control/bulk_msg: timeout usb.c: USB device not accepting new address (error=-110) usb.c: USB new device connect, assigned device number -1 usb_control/bulk_msg: timeout usb.c: USB device not accepting new address (error=-110) usb.c: USB disconnect on device -1 $ cat /proc/bus/usb/drivers hid hub usbdevfs $ cat /proc/bus/usb/devices T: Bus=01 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=12 MxCh= 2 B: Alloc= 0/900 us ( 0%), #Int= 0, #Iso= 0 D: Ver= 1.00 Cls=09(hub ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1 P: Vendor= ProdID= Rev= 0.00 S: Product=USB UHCI Root Hub S: SerialNumber=f300 C:* #Ifs= 1 Cfg#= 1 Atr=40 MxPwr= 0mA I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub E: Ad=81(I) Atr=03(Int.) MxPS= 8 Ivl=255ms The only thing weird on the boot mesg is that I physically only have one USB port but the system is trying to assign 2 devices. Thanks in advance for any help. Eric -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Update: Re: PCMCIA Support for 2.2.19 kernel
Eric Richardson wrote: > > Walt Mankowski wrote: > > > > I'm confused as to how to upgrade my laptop (currently running potato > > 2.2r3) from kernel 2.2.17 to 2.2.19. Which pcmcia-modules package > > should I install? There are four choices: > > > > pcmcia-modules-2.2.19pre17 > > pcmcia-modules-2.2.19pre17-compact > > pcmcia-modules-2.2.19pre17-ide > > pcmcia-modules-2.2.19pre17-idepci > > > > That gives me only two choices for a kernel image: > > > > kernel-image-2.2.19pre17-compact > > kernel-image-2.2.19pre17-idepci > > > > Which of these, if any, should I install? Any idea why there aren't > > any pcmcia-modules packages for the released 2.2.19 kernel? > > I'm not sure what to do so I went ahead and filed a bug report. It > doesn't make > sense to me. It might just be an oversight as the package is not in the > stable archive. I tried to install the pcmcia-modules-2.1.19-2 > I found in unstable and it doesn't work. I'm using 2.2.17 until this is > resolved or I compile them myself. I added the following to /etc/apt/sources.list # proposed deb http://http.us.debian.org/debian dists/potato-proposed-updates/ deb http://non-us.debian.org/debian-non-US dists/potato-proposed-updates/ apt-get install pcmcia-modules-2.2.19 The updated the modules and added pcmcia and also updated the 2.2.19 kernel to one that matches the compiled modules. I've been using this for a while without any trouble that I'm aware of. Eric -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Need PCMCIA help.
Hi, Both my ethernet Controller and the cardbus are using the same interrupt and I'm told this is suboptimal as it is sharing it with USB. PCMCIA is working but USB is not(2.2.19 kernel). How can I update /etc/pcmcia.conf to remedy this? Here is the USB and the PCMCIA dmesg output. The first part of the message prints out options: [pci] [cardbus] [apm] Should this be set to something as well? Thanks for help, Eric usb-uhci.c: USB UHCI at I/O 0xf300, IRQ 10 Linux PCMCIA Card Services 3.1.22 kernel build: 2.2.19 #1 Thu Apr 19 22:35:28 EST 2001 options: [pci] [cardbus] [apm] PCI routing table version 1.0 at 0xfe840 Intel PCIC probe: TI 1225 rev 01 PCI-to-CardBus at slot 00:0a, mem 0x6800 host opts [0]: [serial pci & irq] [pci irq 10] [lat 168/176] [bus 32/34] host opts [1]: [serial pci & irq] [pci irq 10] [lat 168/176] [bus 35/37] ISA irqs (scanned) = 3,4,7,9,11 PCI status changes cs: IO port probe 0x0c00-0x0cff: excluding 0xcf8-0xcff cs: IO port probe 0x0800-0x08ff: excluding 0x800-0x807 cs: IO port probe 0x0100-0x04ff: excluding 0x300-0x307 0x378-0x37f 0x388-0x38f 0x3e8-0x3ff 0x4d0-0x4d7 cs: IO port probe 0x0a00-0x0aff: clean. cs: cb_alloc(bus 35): vendor 0x1011, device 0x0019 ROM image dump: image 0: 0x00-0x0001ff, signature PCIR cs: cb_config(bus 35) fn 0 bar 1: io 0x400-0x47f fn 0 bar 2: mem 0x600c-0x600c007f fn 0 rom: mem 0x6008-0x600b irq 10 cs: cb_enable(bus 35) bridge io map 0 (flags 0x21): 0x400-0x47f bridge mem map 0 (flags 0x1): 0x6008-0x600c0fff tulip_attach(device 23:00.0) tulip.c:v0.91g-ppc 7/16/99 [EMAIL PROTECTED] (modified by [EMAIL PROTECTED] for XIRCOM CBE, fixed by Doug Ledford) eth0: Digital DS21143 Tulip rev 48 at 0x400, 00:10:7A:10:E1:DB, IRQ 10. eth0: EEPROM default media type Autosense. eth0: Index #0 - Media 10baseT (#0) described by a 21142 Serial PHY (2) block. eth0: Index #1 - Media 10baseT-FD (#4) described by a 21142 Serial PHY (2) block. eth0: Index #2 - Media 100baseTx (#3) described by a 21143 SYM PHY (4) block.eth0: Index #3 - Media 100baseTx-FD (#5) described by a 21143 SYM PHY (4) block. cs: memory probe 0xa000-0xa0ff: clean. tty04 at 0x0ae8 (irq = 3) is a 16550A -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Need PCMCIA help.
Petr Hlustik wrote: > > Eric, > > > Both my ethernet Controller and the cardbus are using the same interrupt > > and I'm told this is suboptimal as it is sharing it with USB. PCMCIA is > > working but USB is not(2.2.19 kernel). > > [...] > > > Linux PCMCIA Card Services 3.1.22 > > I do not use USB but debian-proposed-updates also has pcmcia-modules > version 2.1.25, which is the one I tried. Maybe the newer PCMCIA modules > got smarter about sharing the IRQs? I've got proposed in my sources. # apt-get install pcmcia-cs Reading Package Lists... Done Building Dependency Tree... Done Sorry, pcmcia-cs is already the newest version 0 packages upgraded, 0 newly installed, 0 to remove and 1 not upgraded. I already have pcmcia-modules-2.2.19 so I'm not sure what you are refering to. Eric -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Need PCMCIA help.
Petr Hlustik wrote: > > On Thu, May 10, 2001 at 04:29:54PM -0700, Eric Richardson wrote: > > > > I do not use USB but debian-proposed-updates also has pcmcia-modules > > > version 2.1.25, which is the one I tried. Maybe the newer PCMCIA modules > > > got smarter about sharing the IRQs? > > > > I've got proposed in my sources. > > > > # apt-get install pcmcia-cs > > Reading Package Lists... Done > > Building Dependency Tree... Done > > Sorry, pcmcia-cs is already the newest version > > 0 packages upgraded, 0 newly installed, 0 to remove and 1 not upgraded. > > > > I already have pcmcia-modules-2.2.19 so I'm not sure what you are > > refering to. > > To be honest, I did not use apt, I FPTed to > ftp://ftp.debian.org/debian/pool/main/p/pcmcia-cs/ > > which has these guys: > > pcmcia-modules-2.2.19_3.1.25-3k2_i386.deb > pcmcia-modules-2.2.19_3.1.22-0.2potatok4_i386.deb > > I used the top one... > It looks like the 2.2r4 will have the pcmcia added according to the post PCMCIA Support for 2.2.19 kernel Maybe this will help, eric p.s. I'm learning to compile and install custom kernels since alot of people suggest this is the way to go. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: compiling pcmcia-source
Robert Voigt wrote: > > On Thursday 17 May 2001 20:59, Vivek Dasmohapatra wrote: > > I usually use > > > > apt-get install FOO-source > > cd /usr/src/linux > > make-kpkg modules_image > > > > to create the pcmcia/thinkpad/alsa/whatever debs. Have you tried that? > > It says > make-kpkg No such file or directory. > In what package is it? I thought I used it before, don't know what's wrong. It's in kernel-package and here is a good doc that may help. http://newbiedoc.sourceforge.net/system/kernel-pkg.en.html Hope this helps, Eric -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
How to get libgnome 1.2.x for development?
Hi, I'm on stable and trying to compile a program that requires the following: libgnome 1.2.x, gtk+ 1.2.7 and libxml 1.8.x and gnome-print 0.25. I installed the libgnome-dev (which installs libgtk1.2-dev) and libxml-dev which gives me the following: libgnome 1.0.56, gtk+ 1.2.7 and libxml 1.8.x and gnome-print 0.10. I think the gnome-print comes with libgnome. Anyway, I was wondering how I can get the 1.2 libgnome. It looks like it is libgnome32 in testing but I couldn't find any installable packages. Could I put a deb src for testing and then get the source to compile and then install? What package? Will installing the new libs conflict or mess up the current libs? I really don't want to mess up a perfectly good system because I don't know what I am doing. Any help would be appreciated. Eric -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: How to get libgnome 1.2.x for development?
Gabor Zoltan Csejtey wrote: > > HI, > > When you download a debian source package after extracting it you can > find the dependencies in the package-version/debian/control file. I couldn't find this but found a debian directory with all the stuff to make a .deb > > There can be more packages to install or compile again. > > e.g I have the following src URI-s in my /etc/apt/sources.list: > #Sources testing > deb-src ftp://sunsite.uio.no/debian testing main non-free contrib > deb-src ftp://sunsite.uio.no/debian-non-US testing/non-US main non-free contrib Okay, I added these for testing/woody in addition to stable. apt-get source libgnome-dev This gave me version 1.2.13-4 which is good. It wouldn't build. apt-get install xpm4g-dev It is built finally.(It's big) > > You may need: > dpkg-dev - Package building tools for Debian What do I do now? Do I package it some how so I can install it? Of course it has a make install target. Use a ./configure --prefix=PATH and install it via make install somewhere else? When you don't know a process - it stinks. Maybe you know of some documentation for Debian development. Anyway, thank a ton for getting me this far. Eric -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: libgnome-dev 1.2.x - doesn't compile
Gabor Zoltan Csejtey wrote: > > Hi, > > You can compile the debian source with apt with > > apt-get source -b package_name > > or after getting the source you can use: > > dpkg-buildpackage -uc -b > > in the source directory (the source extracted and patched after > downloading). > this command is called by apt-get if you use the -b option. > If you have troubles compiling the source look at the > debian/rules file in your source directory. > There're the commands for compiling the source package. > > After compiling the package source you'll get xxx.deb installable > packages in the directory which contains the source directory. > (i.e. one level up in the directory hiearchy.) Okay, I tried this and it failed. The follow directories are the trouble maker. gnome-libs-1.2.13/intl gnome-libs-1.2.13/gnome-faq These have no Makefile.in so a empty Makefile gets created which fails on the recursive build. Making clean in intl make[2]: Entering directory `/root/gnome-libs-1.2.13/intl' make[2]: *** No rule to make target `clean'. Stop. make[2]: Leaving directory `/root/gnome-libs-1.2.13/intl' make[1]: *** [clean-recursive] Error 1 make[1]: Leaving directory `/root/gnome-libs-1.2.13' make: *** [clean] Error 2 One other thing. I do not have a deb-src to unstable because I thought it might have even a newer version than 1.2.13 and 1.2 is fine. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: libgnome-dev 1.2.x - doesn't compile
Gabor Zoltan Csejtey wrote: > > Hi, > > I downloaded both gnome-libs_1.2.13-6 and gnome-libs_1.2.13-4 sources > from the debian distribution. The location is: > > ftp://ftp.no.debian.org/debian/pool/main/g/gnome-libs/ > > As I see there's a Makefile.in in the > > gnome-libs-1.2.13/intl > > but I couldn't find gnome-libs-1.2.13/gnome-faq directory. > > I tried configure in the gnome-libs-1.2.13 and this made the Makefiles > in gnome-libs-1.2.13/intl too. > > -rw-r--r--1 root root 6514 May 30 12:39 intl/Makefile > -rw-r--r--1 500 500 6455 Mar 16 20:46 intl/Makefile.in > > Gabor > PS. > The source tarball is the same for testing and unstable. The patches > differ: > -rw-r--r--1 csg csg 95498 May 30 12:30 gnome-libs_1.2.13-4.diff.gz > -rw-r--r--1 root root 178896 May 15 16:27 gnome-libs_1.2.13-6.diff.gz I'll add the unstable to sources.list - maybe the makefile is in the unstable diff. Is this just coincidence as I thought testing and unstable used different versions of almost everything? Eric -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: libgnome-dev 1.2.x - doesn't compile
Gabor Zoltan Csejtey wrote: > > Hi, > > I downloaded both gnome-libs_1.2.13-6 and gnome-libs_1.2.13-4 sources > from the debian distribution. The location is: > > ftp://ftp.no.debian.org/debian/pool/main/g/gnome-libs/ > > As I see there's a Makefile.in in the > > gnome-libs-1.2.13/intl > > but I couldn't find gnome-libs-1.2.13/gnome-faq directory. > > I tried configure in the gnome-libs-1.2.13 and this made the Makefiles > in gnome-libs-1.2.13/intl too. > > -rw-r--r--1 root root 6514 May 30 12:39 intl/Makefile > -rw-r--r--1 500 500 6455 Mar 16 20:46 intl/Makefile.in > > Gabor > PS. > The source tarball is the same for testing and unstable. The patches > differ: > -rw-r--r--1 csg csg 95498 May 30 12:30 gnome-libs_1.2.13-4.diff.gz > -rw-r--r--1 root root 178896 May 15 16:27 gnome-libs_1.2.13-6.diff.gz Sorry, but do I have to manually apply the diff? Eric -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: power button dell inspiron 4000
Tim Connors wrote: > > One annoying um, feature, of the dell laptop, is the ability to shut down > immediately upon pressing the power button. I have not found anything on > the web to disable the power button (seems there are lots of references to > toshiba laptops though), has anyone else found anything useful? > > Unfortuneatly, there is nothing in the bios that says "power > switch==off/suspend" - is there a newer bios that fixes this? > If dmesg pumps out something like this, then APM is enabled in the kernel. apm: BIOS version 1.2 Flags 0x03 (Driver version 1.13) Edit /etc/lilo.conf image=/vmlinuz label=Linux read-only append="apm=on" # restricted # alias=1 Add the append line. Then when you halt, APM will shutoff the machine. Hope this helps, Eric -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: PCMCIA Network card up on boot...
Hi Bruce, I installed woody and everything worked fine. When I upgraded to 2.4.x I had the same problem. I am using dhcp and there was no entry for eth0 in /etc/network/interfaces. It now looks like auto lo eth0 iface lo inet loopback iface eth0 inet dhcp This fixed the problem. Of course I needed to use yenta_socket and tulip rather than tulip_cb. I wasn't using hotplug so I can't comment on that. Good luck, Eric Bruce wrote: I would like my wireless PCMCIA network card to be up and running on boot. From what I can gather from the hotplug docs, it should be started via "coldplugging", i.e, by the /etc/init.d/hotplug script which is run at boot time. To get the card to work after a reboot, I have to eject it and reinsert it after I have booted. When I do this, the hotplug scripts do their job and the network card is brought up. I notice that, by default, in runlevel 2, /etc/init.d/hotplug is run at S11, whereas /etc/init.d/pcmcia isn't run until S20. Shouldn't hotplug be run _after_ pcmcia when booting to get an already connected pcmcia device to work on boot?? If so, should I move pcmcia up, or hotplug down, in the boot order?? Am I missing something, or does this (default) configuration mean no coldplugging of PCMCIA devices in Woody? Bruce
Re: Tecra 8100 networking
Bradley Alexander wrote: I just recently reinstalled Woody on my T8100. The first time, I installed using a port replicator. After install, when I booted the machine on the port replicator, it would find the interface and assign the IP address. When I was using the PCMCIA NIC (a Xircom RealPort 16), I had to manually start restart pcmcia. After the rebuild (which I did using the PCMCIA NIC), the box comes up normally when using PCMCIA, but when on the port replicator, I have to do ifcfg eth0 to get the NIC in the replicator up and running. How can I get either nic up and running automagically? Thanks, This may be too obvious but have you checked the file - # /etc/network/interfaces -- configuration file for ifup(8), ifdown(8) auto lo eth0 iface lo inet loopback iface eth0 inet dhcp It should have a entry for each device desired. Eric
Network help for woody/2.4 needed
Hi, I seem to have everything working okay but can't seem to get eth0 to come up automatically on boot. Everything worked fine with 2.2.20 kernel but now with 2.4.18-k6 it won't start without running ifup eth0. I'd really like to get this working the Debian way without hacks or at least understand what is going on. Here is relevant dmesg, module, and /etc/network/interfaces info. I did play around with the interfaces file, looked at the man pages etc. with no luck. Any help is appreciated. Thanks, Eric Linux Kernel Card Services 3.1.22 options: [pci] [cardbus] [pm] PCI: Assigned IRQ 10 for device 00:0a.0 PCI: Assigned IRQ 10 for device 00:0a.1 Yenta IRQ list 0a98, PCI irq10 Socket status: 3059 Yenta IRQ list 0a98, PCI irq10 Socket status: 3069 cs: cb_alloc(bus 5): vendor 0x1011, device 0x0019 PCI: Enabling device 05:00.0 ( -> 0003) Linux Tulip driver version 0.9.15-pre9 (Nov 6, 2001) PCI: Setting latency timer of device 05:00.0 to 64 tulip0: EEPROM default media type Autosense. tulip0: Index #0 - Media 10baseT (#0) described by a 21142 Serial PHY (2) block. tulip0: Index #1 - Media 10baseT-FDX (#4) described by a 21142 Serial PHY (2) block. tulip0: Index #2 - Media 100baseTx (#3) described by a 21143 SYM PHY (4) block. tulip0: Index #3 - Media 100baseTx-FDX (#5) described by a 21143 SYM PHY (4) block. eth0: Digital DS21143 Tulip rev 48 at 0x4800, 00:10:7A:10:E1:8B, IRQ 10. pci_hotplug: PCI Hot Plug PCI Core version: 0.3 --- tulip 36960 1 serial_cs 4384 0 (unused) ds 6432 2 [serial_cs] yenta_socket8128 2 pcmcia_core38496 0 [serial_cs ds yenta_socket] -- # /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 iface eth0 inet dhcp
Re: Network help for woody/2.4 needed
Thanks all, I thought I tried that but must have changed something else at the same time. auto lo eth0 iface lo inet loopback iface eth0 inet dhcp This works fine. You saved me a bunch of time. Eric Stephen Gran wrote: This one time, at band camp, Eric Richardson said: Hi, I seem to have everything working okay but can't seem to get eth0 to come up automatically on boot. Everything worked fine with 2.2.20 kernel but now with 2.4.18-k6 it won't start without running ifup eth0. I'd really like to get this working the Debian way without hacks or at least understand what is going on. Here is relevant dmesg, module, and /etc/network/interfaces info. I did play around with the interfaces file, looked at the man pages etc. with no luck. Any help is appreciated. # /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 iface eth0 inet dhcp Needs a line 'auto eth0' in there to make the interface come up automatically. Steve
Re: PCMCIA Help
Hi Andreas, You might want to try debian-laptop list. I always use the /etc/init.d/networking script or /etc/init.d/pcmcia to start and stop the cardbus. Did you try booting with the card in? Eric Andreas Goesele wrote: Hi, I already lost too much time trying to get PCMCIA work on my laptop (Samsung MV7000, potato, kernel 2.2.19, corega FEther PCC-TXF). The card works under Win98. When I put in the card I get one deep beep, removing it one high beep. The card is recognized and the modules seem to be loaded alright. But ifconfig doesn't show eth0 and consequently a ping results in "network is unreachable". The network information (ip-address, network, netmask, gateway, broadcast) in network.conf is most certainly correct. (But see below under 6.) Trying to run the network script by hand invariably gives: /etc/pcmcia/network start eth0 usage: /etc/pcmcia/network [action] [device name] actions: start check stop suspend resume Follows all the info I could get. (1. system log, 2. cardctl status, 3. cardctl config, 4. cardctl ident, 5. test_setup, 6. test_network, 7. dump_pirq 1) In the system log I have: Oct 13 19:49:43 debi kernel: Linux PCMCIA Card Services 3.1.22 Oct 13 19:49:43 debi kernel: kernel build: 2.2.19 #1 Wed Mar 20 19:41:41 EST 2002 Oct 13 19:49:43 debi kernel: options: [pci] [cardbus] [apm] Oct 13 19:49:43 debi kernel: PCI routing table version 1.0 at 0xfdf60 Oct 13 19:49:43 debi kernel: 00:08.1 -> irq 5 Oct 13 19:49:43 debi kernel: Intel PCIC probe: Oct 13 19:49:43 debi kernel: Ricoh RL5C478 rev 80 PCI-to-CardBus at slot 00:08, mem 0x6800 Oct 13 19:49:43 debi kernel: host opts [0]: [serial irq] [io 3/6/1] [mem 3/6/1] [pci irq 11] [lat 168/176] [bus 32/34] Oct 13 19:49:43 debi kernel: host opts [1]: [serial irq] [io 3/6/1] [mem 3/6/1] [pci irq 5] [lat 168/176] [bus 35/37] Oct 13 19:49:43 debi kernel: ISA irqs (default) = 3,4,7,9,10,12,15 PCI status changes Oct 13 19:49:44 debi kernel: cs: IO port probe 0x0c00-0x0cff: excluding 0xcf8-0xcff Oct 13 19:49:44 debi kernel: cs: IO port probe 0x0800-0x08ff: clean. Oct 13 19:49:44 debi kernel: cs: IO port probe 0x0100-0x04ff: excluding 0x378-0x37f 0x398-0x39f 0x4d0-0x4d7 Oct 13 19:49:44 debi kernel: cs: IO port probe 0x0a00-0x0aff: clean. Oct 13 19:49:44 debi kernel: cs: memory probe 0xa000-0xa0ff: clean. According to the PCMCIA Howto the 10th line should continue and look as for instance: Could that be relevant? 2) Output of cardctl status: Socket 0: 5V 16-bit PC Card function 0: [ready], [wp] Socket 1: no card 3) Output of cardctl config: Socket 0: Vcc 5.0V Vpp1 5.0V Vpp2 5.0V Socket 1: not configured 4) Output of cardctl ident: Socket 0: product info: "corega", "FEther PCC-TXF" manfid: 0xc00f, 0x function: 6 (network) Socket 1: no product info available 5) Output of test_setup: Current kernel: 2.2.19 #1 Wed Mar 20 19:41:41 EST 2002 Module info from /lib/modules/2.2.19/pcmcia/pcmcia_core.o: Linux PCMCIA Card Services 3.1.22 options: [pci] [cardbus] [apm] Startup options from /etc/pcmcia.conf: PCMCIA=yes PCIC=i82365 PCIC_OPTS= CORE_OPTS= CARDMGR_OPTS= Checking current syslog files in /var/log: All PCMCIA messages are in /var/log/syslog. Module status: The PCMCIA kernel modules are loaded correctly. Daemon status: cardmgr is running (process 168) Current socket status from /var/lib/pcmcia/stab: Socket 0: empty Socket 1: empty 6) Output of test_network: PCMCIA network settings are coming from /etc/pcmcia/network.opts. No PCMCIA network interfaces are configured. There is a network device in socket 0: empty 7) Output of dump_pirq: Interrupt routing table found at address 0xfdf60: Version 1.0, size 0x0080 Interrupt router is device 00:07.0 PCI exclusive interrupt mask: 0x [] Compatible router: vendor 0x8086 device 0x122e Device 00:07.0 (slot 0): ISA bridge INTD: link 0x63, irq mask 0x0800 [11] Device 00:08.0 (slot 0): CardBus bridge INTA: link 0x60, irq mask 0x0800 [11] INTB: link 0x61, irq mask 0x0020 [5] Device 00:0b.0 (slot 0): VGA compatible controller INTA: link 0x62, irq mask 0x0400 [10] Device 00:09.0 (slot 0): INTA: link 0x60, irq mask 0x0800 [11] Device 00:0a.0 (slot 0): INTA: link 0x61, irq mask 0x0020 [5] Device 00:00.0 (slot 0): Host bridge INTA: link 0x60, irq mask 0xdef8 [3,4,5,6,7,9,10,11,12,14,15] INTB: link 0x61, irq mask 0x0020 [5] INTC: link 0x62, irq mask 0xdef8 [3,4,5,6,7,9,10,11,12,14,15] INTD: link 0x63, irq mask 0xdef8 [3,4,5,6,7,9,10,11,12,14,15] Interrupt router at 00:07.0: Intel 82443MX PCI-to-ISA bridge PIRQ1 (link 0x60): irq 11 PIRQ2 (link 0x61): irq 5 PIRQ3 (link 0x62): unrouted PIRQ4 (link 0x63): irq 11 Serial IRQ: [enabled] [continuous] [frame=21] [pulse=4] Level mask: 0x0820 [5,11]
Re: pcmcia help?
What does lsmod report? My networking stuff looks like this for 2.2.x kernel. [EMAIL PROTECTED]:~/app$ lsmod Module Size Used by serial_cs 4980 0 (unused) tulip_cb 30104 2 cb_enabler 2296 2 [tulip_cb] ds 6028 2 [serial_cs cb_enabler] i82365 21072 2 pcmcia_core42384 0 [serial_cs cb_enabler ds i82365] If yours is not similar then you should run modconf as root and select some modules. Use the pcnet_cs as suggested by Bruce instead of tulip_cb as in my situation. The serial_cs is for my modem card I believe. Hope this helps, Eric p.s. unload any modules that you don't need when running modconf if the drivers won't load. Andreas Goesele wrote: Hi, I already lost much too much time trying to get PCMCIA work on my laptop (Samsung MV7000, potato, kernel 2.2.19, corega FEther PCC-TXF). The card works under Win98. When I put in the card, I get one deep beep, removing it one high beep. The card is recognized and the modules seem to be loaded alright. But ifconfig doesn't show eth0 and consequently a ping results in "network is unreachable". The network information (ip-address, network, netmask, gateway, broadcast) in network.conf is most certainly correct. (But see below under 6.) Trying to run the network script by hand invariably gives: /etc/pcmcia/network start eth0 usage: /etc/pcmcia/network [action] [device name] actions: start check stop suspend resume As I have exhausted all my possibility (re-reading various times the PCMCIA-HOWTO, playing around with various settings ...) I would be very grateful for some help! Follows all the info I could get. (1. system log, 2. cardctl status, 3. cardctl config, 4. cardctl ident, 5. test_setup, 6. test_network, 7. dump_pirq 1) In the system log I have: Oct 13 19:49:43 debi kernel: Linux PCMCIA Card Services 3.1.22 Oct 13 19:49:43 debi kernel: kernel build: 2.2.19 #1 Wed Mar 20 19:41:41 EST 2002 Oct 13 19:49:43 debi kernel: options: [pci] [cardbus] [apm] Oct 13 19:49:43 debi kernel: PCI routing table version 1.0 at 0xfdf60 Oct 13 19:49:43 debi kernel: 00:08.1 -> irq 5 Oct 13 19:49:43 debi kernel: Intel PCIC probe: Oct 13 19:49:43 debi kernel: Ricoh RL5C478 rev 80 PCI-to-CardBus at slot 00:08, mem 0x6800 Oct 13 19:49:43 debi kernel: host opts [0]: [serial irq] [io 3/6/1] [mem 3/6/1] [pci irq 11] [lat 168/176] [bus 32/34] Oct 13 19:49:43 debi kernel: host opts [1]: [serial irq] [io 3/6/1] [mem 3/6/1] [pci irq 5] [lat 168/176] [bus 35/37] Oct 13 19:49:43 debi kernel: ISA irqs (default) = 3,4,7,9,10,12,15 PCI status changes Oct 13 19:49:44 debi kernel: cs: IO port probe 0x0c00-0x0cff: excluding 0xcf8-0xcff Oct 13 19:49:44 debi kernel: cs: IO port probe 0x0800-0x08ff: clean. Oct 13 19:49:44 debi kernel: cs: IO port probe 0x0100-0x04ff: excluding 0x378-0x37f 0x398-0x39f 0x4d0-0x4d7 Oct 13 19:49:44 debi kernel: cs: IO port probe 0x0a00-0x0aff: clean. Oct 13 19:49:44 debi kernel: cs: memory probe 0xa000-0xa0ff: clean. According to the PCMCIA Howto the 10th line should continue and look as for instance: Could that be relevant? 2) Output of cardctl status: Socket 0: 5V 16-bit PC Card function 0: [ready], [wp] Socket 1: no card 3) Output of cardctl config: Socket 0: Vcc 5.0V Vpp1 5.0V Vpp2 5.0V Socket 1: not configured 4) Output of cardctl ident: Socket 0: product info: "corega", "FEther PCC-TXF" manfid: 0xc00f, 0x function: 6 (network) Socket 1: no product info available 5) Output of test_setup: Current kernel: 2.2.19 #1 Wed Mar 20 19:41:41 EST 2002 Module info from /lib/modules/2.2.19/pcmcia/pcmcia_core.o: Linux PCMCIA Card Services 3.1.22 options: [pci] [cardbus] [apm] Startup options from /etc/pcmcia.conf: PCMCIA=yes PCIC=i82365 PCIC_OPTS= CORE_OPTS= CARDMGR_OPTS= Checking current syslog files in /var/log: All PCMCIA messages are in /var/log/syslog. Module status: The PCMCIA kernel modules are loaded correctly. Daemon status: cardmgr is running (process 168) Current socket status from /var/lib/pcmcia/stab: Socket 0: empty Socket 1: empty 6) Output of test_network: PCMCIA network settings are coming from /etc/pcmcia/network.opts. No PCMCIA network interfaces are configured. There is a network device in socket 0: empty 7) Output of dump_pirq: Interrupt routing table found at address 0xfdf60: Version 1.0, size 0x0080 Interrupt router is device 00:07.0 PCI exclusive interrupt mask: 0x [] Compatible router: vendor 0x8086 device 0x122e Device 00:07.0 (slot 0): ISA bridge INTD: link 0x63, irq mask 0x0800 [11] Device 00:08.0 (slot 0): CardBus bridge INTA: link 0x60, irq mask 0x0800 [11] INTB: link 0x61, irq mask 0x0020 [5] Device 00:0b.0 (slot 0): VGA compatible controller INTA: link 0x62, irq mask 0x0400 [10] Device 00:09.0 (slot 0): INTA: link 0x60, irq mask 0x0800 [11] Device 00:0a.0 (slot 0): IN
Re: PCMCIA Help
Hi Andreas, You might want to try debian-laptop list. I always use the /etc/init.d/networking script or /etc/init.d/pcmcia to start and stop the cardbus. Did you try booting with the card in? Eric Andreas Goesele wrote: > Hi, > > I already lost too much time trying to get PCMCIA work on my laptop > (Samsung MV7000, potato, kernel 2.2.19, corega FEther PCC-TXF). The > card works under Win98. > > When I put in the card I get one deep beep, removing it one high > beep. The card is recognized and the modules seem to be loaded > alright. But ifconfig doesn't show eth0 and consequently a ping > results in "network is unreachable". The network information > (ip-address, network, netmask, gateway, broadcast) in network.conf is > most certainly correct. (But see below under 6.) > > Trying to run the network script by hand invariably gives: > > /etc/pcmcia/network start eth0 > > usage: /etc/pcmcia/network [action] [device name] > actions: start check stop suspend resume > > Follows all the info I could get. (1. system log, 2. cardctl status, > 3. cardctl config, 4. cardctl ident, 5. test_setup, 6. test_network, > 7. dump_pirq > > 1) In the system log I have: > > Oct 13 19:49:43 debi kernel: Linux PCMCIA Card Services 3.1.22 > Oct 13 19:49:43 debi kernel: kernel build: 2.2.19 #1 Wed Mar 20 19:41:41 EST 2002 > Oct 13 19:49:43 debi kernel: options: [pci] [cardbus] [apm] > Oct 13 19:49:43 debi kernel: PCI routing table version 1.0 at 0xfdf60 > Oct 13 19:49:43 debi kernel: 00:08.1 -> irq 5 > Oct 13 19:49:43 debi kernel: Intel PCIC probe: > Oct 13 19:49:43 debi kernel: Ricoh RL5C478 rev 80 PCI-to-CardBus at slot 00:08, >mem 0x6800 > Oct 13 19:49:43 debi kernel: host opts [0]: [serial irq] [io 3/6/1] [mem 3/6/1] >[pci irq 11] [lat 168/176] [bus 32/34] > Oct 13 19:49:43 debi kernel: host opts [1]: [serial irq] [io 3/6/1] [mem 3/6/1] >[pci irq 5] [lat 168/176] [bus 35/37] > Oct 13 19:49:43 debi kernel: ISA irqs (default) = 3,4,7,9,10,12,15 PCI status >changes > Oct 13 19:49:44 debi kernel: cs: IO port probe 0x0c00-0x0cff: excluding 0xcf8-0xcff > Oct 13 19:49:44 debi kernel: cs: IO port probe 0x0800-0x08ff: clean. > Oct 13 19:49:44 debi kernel: cs: IO port probe 0x0100-0x04ff: excluding 0x378-0x37f >0x398-0x39f 0x4d0-0x4d7 > Oct 13 19:49:44 debi kernel: cs: IO port probe 0x0a00-0x0aff: clean. > Oct 13 19:49:44 debi kernel: cs: memory probe 0xa000-0xa0ff: clean. > > According to the PCMCIA Howto the 10th line should continue and look > as for instance: > > Could that be relevant? > > 2) Output of cardctl status: > > Socket 0: > 5V 16-bit PC Card > function 0: [ready], [wp] > Socket 1: > no card > > 3) Output of cardctl config: > > Socket 0: > Vcc 5.0V Vpp1 5.0V Vpp2 5.0V > Socket 1: > not configured > > 4) Output of cardctl ident: > > Socket 0: > product info: "corega", "FEther PCC-TXF" > manfid: 0xc00f, 0x > function: 6 (network) > Socket 1: > no product info available > > 5) Output of test_setup: > > Current kernel: 2.2.19 #1 Wed Mar 20 19:41:41 EST 2002 > Module info from /lib/modules/2.2.19/pcmcia/pcmcia_core.o: > Linux PCMCIA Card Services 3.1.22 > options: [pci] [cardbus] [apm] > > Startup options from /etc/pcmcia.conf: > PCMCIA=yes > PCIC=i82365 > PCIC_OPTS= > CORE_OPTS= > CARDMGR_OPTS= > > Checking current syslog files in /var/log: > All PCMCIA messages are in /var/log/syslog. > > Module status: > The PCMCIA kernel modules are loaded correctly. > > Daemon status: > cardmgr is running (process 168) > > Current socket status from /var/lib/pcmcia/stab: > Socket 0: empty > Socket 1: empty > > 6) Output of test_network: > > PCMCIA network settings are coming from /etc/pcmcia/network.opts. > No PCMCIA network interfaces are configured. > > There is a network device in socket 0: > empty > > 7) Output of dump_pirq: > > Interrupt routing table found at address 0xfdf60: > Version 1.0, size 0x0080 > Interrupt router is device 00:07.0 > PCI exclusive interrupt mask: 0x [] > Compatible router: vendor 0x8086 device 0x122e > > Device 00:07.0 (slot 0): ISA bridge > INTD: link 0x63, irq mask 0x0800 [11] > > Device 00:08.0 (slot 0): CardBus bridge > INTA: link 0x60, irq mask 0x0800 [11] > INTB: link 0x61, irq mask 0x0020 [5] > > Device 00:0b.0 (slot 0): VGA compatible controller > INTA: link 0x62, irq mask 0x0400 [10] > > Device 00:09.0 (slot 0): > INTA: link 0x60, irq mask 0x0800 [11] > > Device 00:0a.0 (slot 0): > INTA: link 0x61, irq mask 0x0020 [5] > > Device 00:00.0 (slot 0): Host bridge > INTA: link 0x60, irq mask 0xdef8 [3,4,5,6,7,9,10,11,12,14,15] > INTB: link 0x61, irq mask 0x0020 [5] > INTC: link 0x62, irq mask 0xdef8 [3,4,5,6,7,9,10,11,12,14,15] > INTD: link 0x63, irq mask 0xdef8 [3,4,5,6,7,9,10,11,12,14,15] > > Interrupt router at 00:07.0: Intel 82443MX PCI-to-ISA bridge > PIRQ1 (link 0x60): irq 11 > PIRQ2 (link 0x61): irq 5 > PIRQ3 (link 0x62): unroute
Re: pcmcia help?
What does lsmod report? My networking stuff looks like this for 2.2.x kernel. maxwell@maxwell:~/app$ lsmod Module Size Used by serial_cs 4980 0 (unused) tulip_cb 30104 2 cb_enabler 2296 2 [tulip_cb] ds 6028 2 [serial_cs cb_enabler] i82365 21072 2 pcmcia_core42384 0 [serial_cs cb_enabler ds i82365] If yours is not similar then you should run modconf as root and select some modules. Use the pcnet_cs as suggested by Bruce instead of tulip_cb as in my situation. The serial_cs is for my modem card I believe. Hope this helps, Eric p.s. unload any modules that you don't need when running modconf if the drivers won't load. Andreas Goesele wrote: > Hi, > > I already lost much too much time trying to get PCMCIA work on my > laptop (Samsung MV7000, potato, kernel 2.2.19, corega FEther > PCC-TXF). The card works under Win98. > > When I put in the card, I get one deep beep, removing it one high > beep. The card is recognized and the modules seem to be loaded > alright. But ifconfig doesn't show eth0 and consequently a ping > results in "network is unreachable". The network information > (ip-address, network, netmask, gateway, broadcast) in network.conf is > most certainly correct. (But see below under 6.) > > Trying to run the network script by hand invariably gives: > > /etc/pcmcia/network start eth0 > > usage: /etc/pcmcia/network [action] [device name] > actions: start check stop suspend resume > > As I have exhausted all my possibility (re-reading various times the > PCMCIA-HOWTO, playing around with various settings ...) I would be > very grateful for some help! > > Follows all the info I could get. (1. system log, 2. cardctl status, > 3. cardctl config, 4. cardctl ident, 5. test_setup, 6. test_network, > 7. dump_pirq > > 1) In the system log I have: > > Oct 13 19:49:43 debi kernel: Linux PCMCIA Card Services 3.1.22 > Oct 13 19:49:43 debi kernel: kernel build: 2.2.19 #1 Wed Mar 20 19:41:41 EST 2002 > Oct 13 19:49:43 debi kernel: options: [pci] [cardbus] [apm] > Oct 13 19:49:43 debi kernel: PCI routing table version 1.0 at 0xfdf60 > Oct 13 19:49:43 debi kernel: 00:08.1 -> irq 5 > Oct 13 19:49:43 debi kernel: Intel PCIC probe: > Oct 13 19:49:43 debi kernel: Ricoh RL5C478 rev 80 PCI-to-CardBus at slot 00:08, >mem 0x6800 > Oct 13 19:49:43 debi kernel: host opts [0]: [serial irq] [io 3/6/1] [mem 3/6/1] >[pci irq 11] [lat 168/176] [bus 32/34] > Oct 13 19:49:43 debi kernel: host opts [1]: [serial irq] [io 3/6/1] [mem 3/6/1] >[pci irq 5] [lat 168/176] [bus 35/37] > Oct 13 19:49:43 debi kernel: ISA irqs (default) = 3,4,7,9,10,12,15 PCI status >changes > Oct 13 19:49:44 debi kernel: cs: IO port probe 0x0c00-0x0cff: excluding 0xcf8-0xcff > Oct 13 19:49:44 debi kernel: cs: IO port probe 0x0800-0x08ff: clean. > Oct 13 19:49:44 debi kernel: cs: IO port probe 0x0100-0x04ff: excluding 0x378-0x37f >0x398-0x39f 0x4d0-0x4d7 > Oct 13 19:49:44 debi kernel: cs: IO port probe 0x0a00-0x0aff: clean. > Oct 13 19:49:44 debi kernel: cs: memory probe 0xa000-0xa0ff: clean. > > According to the PCMCIA Howto the 10th line should continue and look > as for instance: > > Could that be relevant? > > 2) Output of cardctl status: > > Socket 0: > 5V 16-bit PC Card > function 0: [ready], [wp] > Socket 1: > no card > > 3) Output of cardctl config: > > Socket 0: > Vcc 5.0V Vpp1 5.0V Vpp2 5.0V > Socket 1: > not configured > > 4) Output of cardctl ident: > > Socket 0: > product info: "corega", "FEther PCC-TXF" > manfid: 0xc00f, 0x > function: 6 (network) > Socket 1: > no product info available > > 5) Output of test_setup: > > Current kernel: 2.2.19 #1 Wed Mar 20 19:41:41 EST 2002 > Module info from /lib/modules/2.2.19/pcmcia/pcmcia_core.o: > Linux PCMCIA Card Services 3.1.22 > options: [pci] [cardbus] [apm] > > Startup options from /etc/pcmcia.conf: > PCMCIA=yes > PCIC=i82365 > PCIC_OPTS= > CORE_OPTS= > CARDMGR_OPTS= > > Checking current syslog files in /var/log: > All PCMCIA messages are in /var/log/syslog. > > Module status: > The PCMCIA kernel modules are loaded correctly. > > Daemon status: > cardmgr is running (process 168) > > Current socket status from /var/lib/pcmcia/stab: > Socket 0: empty > Socket 1: empty > > 6) Output of test_network: > > PCMCIA network settings are coming from /etc/pcmcia/network.opts. > No PCMCIA network interfaces are configured. > > There is a network device in socket 0: > empty > > 7) Output of dump_pirq: > > Interrupt routing table found at address 0xfdf60: > Version 1.0, size 0x0080 > Interrupt router is device 00:07.0 > PCI exclusive interrupt mask: 0x [] > Compatible router: vendor 0x8086 device 0x122e > > Device 00:07.0 (slot 0): ISA bridge > INTD: link 0x63, irq mask 0x0800 [11] > > Device 00:08.0 (slot 0): CardBus bridge > INTA: link 0x60, irq mask
Re: PCMCIA Network card up on boot...
Hi Bruce, I installed woody and everything worked fine. When I upgraded to 2.4.x I had the same problem. I am using dhcp and there was no entry for eth0 in /etc/network/interfaces. It now looks like auto lo eth0 iface lo inet loopback iface eth0 inet dhcp This fixed the problem. Of course I needed to use yenta_socket and tulip rather than tulip_cb. I wasn't using hotplug so I can't comment on that. Good luck, Eric Bruce wrote: I would like my wireless PCMCIA network card to be up and running on boot. From what I can gather from the hotplug docs, it should be started via "coldplugging", i.e, by the /etc/init.d/hotplug script which is run at boot time. To get the card to work after a reboot, I have to eject it and reinsert it after I have booted. When I do this, the hotplug scripts do their job and the network card is brought up. I notice that, by default, in runlevel 2, /etc/init.d/hotplug is run at S11, whereas /etc/init.d/pcmcia isn't run until S20. Shouldn't hotplug be run _after_ pcmcia when booting to get an already connected pcmcia device to work on boot?? If so, should I move pcmcia up, or hotplug down, in the boot order?? Am I missing something, or does this (default) configuration mean no coldplugging of PCMCIA devices in Woody? Bruce -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Tecra 8100 networking
Bradley Alexander wrote: I just recently reinstalled Woody on my T8100. The first time, I installed using a port replicator. After install, when I booted the machine on the port replicator, it would find the interface and assign the IP address. When I was using the PCMCIA NIC (a Xircom RealPort 16), I had to manually start restart pcmcia. After the rebuild (which I did using the PCMCIA NIC), the box comes up normally when using PCMCIA, but when on the port replicator, I have to do ifcfg eth0 to get the NIC in the replicator up and running. How can I get either nic up and running automagically? Thanks, This may be too obvious but have you checked the file - # /etc/network/interfaces -- configuration file for ifup(8), ifdown(8) auto lo eth0 iface lo inet loopback iface eth0 inet dhcp It should have a entry for each device desired. Eric -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
