[Cooker] minicom and ppp broken for pcmcia modems
This is a bug I spotted after installing MD8.2 on an old laptop. (Yes, I have seen the hotplug errata :) The same version of minicom and ppp are in cooker still, I think. My laptop (HP Omnibook CS5500) hasPCMCIA bridgeCirrus Logic CL6729 (rev e2). The PCMCIA modem card is a Pace NB56 56K card. I also have a Prolink 1436C 33.6K card, which behaves the same way. (These are both full hardware modems and work fine with kppp.) My PCMCIA net card works fine, and the modems both work with kppp (ie, the hardware is fine!). I have configured my modem and ppp scriptsfrom a shellusing netconf. My problem is that neither minicom, nor the ifup/usernetctl command line tools can communicate with the modem. As root, minicom starts, but the modem does not reply "OK" to the initialisation string, or to "AT". ifup leaves this message in the logs: May 13 08:47:09 waterloo ifup-ppp: pppd started for ppp0 on /dev/modem at 115200May 13 08:47:09 waterloo pppd[2375]: pppd 2.4.1 started by root, uid 0May 13 08:47:11 waterloo pppd[2375]: Connect script failedMay 13 08:47:12 waterloo pppd[2375]: Exit. Note that the script has "failed" before an attempt to dial a number. If I create and install a new minicom RPM (rpm -ba minicom.spec) from the SRPM, minicom is still broken. If I just extract the raw minicom source from the SRPM and compile that (./configure, make), then then minicom works fine -- the Mandrake rpm build script is doing something that stops minicom from communicating with my PCMCIA modem.What would I need to recompile to get ifup working (I *need* this ...)? I tried ppp, but it didn't make any difference. Steven
[Cooker] minicom and ppp broken for pcmcia modems
[Reposted in plain text] This is a bug I spotted after installing MD8.2 on an old laptop. (Yes, I have seen the hotplug errata :) The same version of minicom and ppp are in cooker still, I think. My laptop (HP Omnibook CS5500) has PCMCIA bridge Cirrus Logic CL6729 (rev e2). The PCMCIA modem card is a Pace NB56 56K card. I also have a Prolink 1436C 33.6K card, which behaves the same way. (These are both full hardware modems and work fine with kppp.) My PCMCIA net card works fine, and the modems both work with kppp (ie, the hardware is fine!). I have configured my modem and ppp scripts from a shell using netconf. My problem is that neither minicom, nor the ifup/usernetctl command line tools can communicate with the modem. As root, minicom starts, but the modem does not reply OK to the initialisation string, or to AT. ifup leaves this message in the logs: May 13 08:47:09 waterloo ifup-ppp: pppd started for ppp0 on /dev/modem at 115200 May 13 08:47:09 waterloo pppd[2375]: pppd 2.4.1 started by root, uid 0 May 13 08:47:11 waterloo pppd[2375]: Connect script failed May 13 08:47:12 waterloo pppd[2375]: Exit. Note that the script has failed before an attempt to dial a number. If I create and install a new minicom RPM (rpm -ba minicom.spec) from the SRPM, minicom is still broken. If I just extract the raw minicom source from the SRPM and compile that (./configure, make), then then minicom works fine -- the Mandrake rpm build script is doing something that stops minicom from communicating with my PCMCIA modem. What would I need to recompile to get ifup working (I *need* this ...)? I tried ppp, but it didn't make any difference. Steven
Re: [Cooker] minicom and ppp broken for pcmcia modems
andrej wrote == My problem is that neither minicom, nor the ifup/usernetctl command line tools can communicate with the modem. As root, minicom starts, but the modem does not reply OK to the initialisation string, or to AT. == First, do not post in HTML. Second, what strace shows? strace -f -o /tmp/foo minicom Thanks for the tips. I tested 2 minicoms, minicom.mdk, (renamed from the Mandrake RPM minicom), and minicom.sjm that I built from the source out of the SRPM. They both used the same minirc.dfl configuration file: pr port/dev/ttyS1 [[[WRONG]]] pu baudrate230400 (It looks like I configured this wrongly, the pr port value should be /dev/ttyS2.) The strace logs are both big. The only obvious difference to my eyes is that the minicom.sjm opened /dev/modem, ignoring the config file. On my computer /dev/modem is linked to /dev/tts/2, which is correct, which is why my compiled version worked. Odd behaviour, but I can't claim the minicom rpm package is broken any more, as both versions of minicom now work with a corrected minirc.dfl. Which leaves me stumped about why ifup ppp0 is not working: May 28 23:37:14 waterloo ifup-ppp: pppd started for ppp0 on /dev/modem at 115200 May 28 23:37:14 waterloo pppd[12382]: pppd 2.4.1 started by root, uid 0 May 28 23:37:15 waterloo pppd[12382]: Connect script failed May 28 23:37:16 waterloo pppd[12382]: Exit. I think I'll sleep on it ...
Re: [Cooker] Network bootdisk of 8.2 doesn't work
Subject: Re: [Cooker] Network bootdisk of 8.2 doesn't work Yes, I know, it's a little bit late - but I just discovered that the network.img from the 8.2 download edition does not work. I've created a boot disk with this image, and the system doesn't start - it hangs shortly after syslinux is displayed. It worked fine for me. Also fine for me using pcmcia network card in a laptop ...
Re: [Cooker] 2.2.3a printing problems: no printing from Word, spools taking up all CPU on clients
From: Buchan Milne [EMAIL PROTECTED] I think Sylvestre is still away on business for the rest of this week, so I will field this one for the moment. Thanks ... Unfortunately, I don't have enough machines available (at work) to be able to test your exact setup, but I have recompiled 2.2.3a-6mdk for Mandrake 8.1 (using rpm --rebuild --with mdk81 on the srpm), and tested it on our (non pdc) production print server. It has been running for a week with no problems. Off topic, but: I'd been using the verison from cooker on our PDC which is/was an 8.0 install. Why bother rebuilding the src RPM? Anyway, the testing I'm describing here is with a clean 8.2 beta 3, as I mentioned before. It is on a machine that is configured as a member of the domain, sharing drivers for the same network printer as the PDC. Please note that we had problems with our DJ970 (crashing of MS Word 97 in printer setup) when we were using the NT4 HP supplied drivers with Windows 2000 on samba-2.2.2. This stopped after we used the drivers supplied with Windows. This sounds more like my situation, except I have no problems with 2.2.2 :/ The Windows drivers don't normally offer all the features (ie booklet printing), although I've not looked at them for this particular printer. I believe from your mails on the samba list that you were using the same drivers with samba-2.2.2 and samba-2.2.3a? Is this correct? On the samba list I described problems on a Mandrake 8.0 PDC server with the samba-2.2.3a-[356]mdk (from cooker) vs samba-2.2.2-3.2mdk (from updates/8.1/RPMS), both with exactly the same drivers (from the HP CDrom, I think). Then I replicated the 2.2.3a behaviour with a clean install of MD8.2b3, 2.2.3a-6mdk Samba RPM, and the latest drivers from the HP web site. (The new test PC is a member of the domain, not the PDC). The printer is an HP2200dn plugged straight in to our LAN. Unfortunately 2.2.2 is itself not without problems. There is a locking race (gave us a number of problems here), and issues with winbind (memory leak, domain controller hits) that we would prefer to avoid. My troubles with 2.2.2 have been less visible that this printing problem :( I installed them while logged in to a Win2000 workstation as user sjm. (A pain in the ass - I had to find a Windows 2000 server CD to complete the install ... ?!?) This is incorrect, Windows 2000 believes you need the CD, but only to convince you you need Windows 2000 Server. You should point it at the drivers, or if you have installed the printer driver locally, or if they came with Windows 2000, you can point it at %windir%\inf (ie C:\WINNT\Inf) Well, first I tried pointing Windows at the downloaded drivers, and the drivers loaded on to the Samba server didn't work. When I supplied an MSDN Win2K install DVD, they did work. I wasn't concentrating very hard at that point, so feel free to be sceptical :) Thanks for the %windir%\inf tip - that will be useful in the future. If you have the option to look at this again, could you just run top on the samba box at this stage, and see if your smb is racing? It generated 5Mb of *compressed* logs, so it was doing something! If I get the chance, I'll check with top. I'll send the samba and client configs seperately ... Thanks for your time, Steven
Re: [Cooker] install report 8.2b3 , the martian invasion
on the 'net. Everybody Apache user I know (that use it on workstations) do the same things. I agree that this will cause annoy more people than it will help .. imho Steven
Re: [Cooker] boot catalog for creating ISOs from cooker
Subject: [Cooker] boot catalog for creating ISOs from cooker Some time ago Troels Liebe Bentsen posted some scripts here to create ISO images from a cooker mirror. In there he calls mkisofs -c images/boot.cat, but in the current cooker there's no images/boot.cat. The boot cat is created by mkisofs, any existing boot.cat will get overwritten, so you don't need there to be an existing one. It is only made for bootable CD disks; I don't know exactly how it is used, but I guess it is just a list of files that to load on bootup. Steven
Re: [Cooker] Curious Issue with Beta and win98 (maybe)
Now, I cannot, no matter what even boot windows 98. Not from CD, floppy or hard disk. Has *anyone* seen anything like this? I am running an Athlon K7 800 on a KT133 Motherboard I had a similar-sounding problem (Duron 650, MSI 6330 MoBo/KT133 Chipset); fixed by resetting my bios changes back to factory default settings. I think in my case it was because I have an LS120, but no floppy, and it was trying to boot from floppy. I'm not sure how an OS install could have affected your bios settings though ... Good luck, Steven
[Cooker] kernel-source rpm and pcmcia
Hello, I just grabbed kernel source 2.2.17-1mdk, kernel headers, and dev86 rpms from cooker to compile a new kernel. When I changed to the pcmcia directory to ./Configure, make all, make install, it insisted on installing all the modules and man pages in to /home/chmou/rpm/tmp/kernel-2.2.17-1mdk-root/. Some mistake?? Steven
Re: [Cooker] CD vs FTP download
Thanks Guillaume, Is it possible to split the "extra" RPMS in to a seperate directory to make it easier to build my CDs? We cannot do this; because it would revert to the problem we had the last 15 days, the FTP install will hang waiting for you to "change the media".. Can't the installer be tweaked to look for an "RPMS2" directory before it prompts for new media? You have several solutions: . d/l an ISO image OK, but unweildy, especially over a 64K line. (At home I have unmetered access, but I get disconnected every 2 hours ... Sometimes reget appears to work, but my downloaded file is sometimes corrupt -- so I like do download lots of smaller files.) Also, I'd like to track updates more closely than the ISO images allow. . split the rpm's in two separate directories; use the "rpmslist" file for that. How does the rpmslist file help me? While I was looking for the rpmslist file I found this link http://www.mandrake.com/drakx/README which has the instructions for making updates CDs ... with the graphical installer, which I was just about to ask. But I can't find any mention of what the directory structure of the 2nd CD is. Can someone post that for me? Steven
[Cooker] CD vs FTP download
Hi, I'm a bit confused by the new larger Mandrake distribution. I download my Mandrake cooker over a 64K ISDN line. Because I download from the ftp site, it doesn't matter if the download gets interupted, for instace by a new RPM going in to the archive. When it's finished I can resync the archive, run mkhdlist, and burn it to CD But I can't do this anymore as all the RPMS are in one directory, so it's too big for a CD. (It's also too big for the parittion I download to !) Is it possible to split the "extra" RPMS in to a seperate directory to make it easier to build my CDs? Otherwise, how can I tell which RPMS are the extra ones? Steven
Re: [Cooker] Suugestion for new utility
Maybe- how would I use "tee" to run "startx" and save the error messages to a text file? I normally just send stuff straight to the log file with : startx x.log maybe : startx x.log would capture more detail. If you need to see these messages from within X just open a term and run : tail -f x.out'
[Cooker] Install fails to set up LAN/ethernet if PCI ISDN present
Last synced with ftp.sunet.se at 22:00 (BST) May 25 I have a "Billion" PCI ISDN adaptor and a Realtek 8139 ethernet card in my machine. If I try to select the "Configure LAN" option during install, it fails and prints the following to console ... (copied out by hand, might be a couple of typos!) * starting step `configureNetwork' * pci probe found 2 net devices * pcmcia probe found 0 net devices * found driber for rtl8139 * found driver for unknown * running: insmod unknown * running: extract_archive /lib/modules /tmp unkown.o * warning: insmod unknown failed at /usr/bin/perl-install/modules.pm line 358. * starting step `configureNetwork' ...
