[Cooker] 9.2 MEDIAS - MEDIA
Hello, Just a minor QA correction before 9.2 gets released. There are many instances of medias in the locales and in the title Software Medias Manager. There is no such word. Media is already a plural and should be used instead. Keep up the great work! Alvin
[Cooker] ADS Pyro ieee1394 WebCam configuration
Hello Cookers, Is anyone using the ADS Pyro 1394 (firewire) webcam with Cooker or other recent Mandrake releases? If so, would you let me know or post your configuration and what works/doesn't work for you. I have the system recognizing the 1394 device when it is plugged in, but haven't been able to see video or capture frames with it yet... I've added video1394 and raw1394 modules to the /etc/modules file, and # lsmod |grep 1394returns: raw139417144 0 video1394 13824 0 (unused) ohci1394 19048 0 [video1394] ieee1394 45900 0 [raw1394 video1394 ohci1394] When I plug the camera into the firewire card, the following lines get logged by dmesg: ieee1394: SelfID completion called outside of bus reset! ieee1394: Device added: Node[01:1023] GUID[0050c510661f] [Unknown] I also got the program coriander (coriander-0.99.1.tar.gz from http://www.tele.ucl.ac.be/PEOPLE/DOUXCHAMPS/ieee1394/coriander/ ), and it clean-compiles, but it segfaults immediately with a gnome popup error. Thanks much for any ideas, Alvin Austin ( aamc AT crlogic DOT com )
[Cooker] NETWORK.IMG nfs mount point problem?
I am seeing a little problem when installing by nfs using the network.img floppy on the current cooker (as on the mirror site at Feb 24 0300 UTC). The server has the cooker path as: (server):/mirror/mdk/cooker/cooker/i586/Mandrake/RPMS contrib is located at: (server):/mirror/mdk/cooker/contrib/i586/ The contrib directory is symbolically linked as: (server):/mirror/mdk/cooker/cooker/i586/Mandrake/RPMS2 - ../../../contrib/i586/ This is the same as on the mirror site. When the install starts, and the install path is specified as: Server: (server) Path: /mirror/mdk/cooker/cooker/i586 ... the mount is made as: (server):/mirror/mdk/cooker/contrib/i586 mounted on /tmp/image The install proceeds, but gives package errors when it comes to installing anything from the contrib (RPMS2) area (for instance apache-1.3), because the RPMS2 symbolic link to contrib is outside the scope of the mount point. Install should mount at a higher level, such as: (server):/mirror/mdk/cooker/ mounted on /tmp/image/cooker/i586 and then: cooker would be found at /tmp/image/coooker/i586/Mandrake and contribs would be properly found at /tmp/image/contrib/i586 (via the symbolic link from RPMS2) *Or* should we be possibly be specifying a different directory path originally, such that the installer would be able to figure this out properly? Of course it is possible to work around this by moving contrib around to get rid of the RPMS2 backward symbolic link just before installation, and restoring it afterwards so that the mirroring still works, but it would be better to have things just work using the directory structure on the mirrors... Thanks for any ideas on this one... Alvin
[Cooker] aic7xxx_old installation problems
Hi All, I'm trying to install the latest cooker onto a SCSI-only machine (even the CDROM is SCSI). The machine has an adaptec AIC-7895 host adaptor on the motherboard, which *requires* the aic7xxx_old driver. Unfortunately, this is not an option in expert mode (only the aic7xxx driver is given as an option). The machine hangs badly when the aic7xxx driver tries to load. === PLEASE add the aic7xxx_old driver to the scsi host adapter list for expert mode. There are many, many machines out there that require this older driver. === Things go downhill with the other boot disks. - The hd-2.2.19-BADZ5 and the network-2.2.19-BADZ5 both let you install Mandrake, but don't install the aic7xxx_old driver into the initrd.img (the aic7xxx gets installed and then you can't boot). - If you try to use the 2.2.19 hd or network images in rescue mode (to try and run mkinitrd to add the aic7xxx_old driver), many modules don't load properly, because the /modules/modules.cz on these images is for the 2.4.* kernels not for 2.2.19. The worst thing is that the loop module cannot be loaded, which breaks mkinitrd. The error message is: # modprobe loop extracting aes.o /tmp/aes.o: kernel-module version mismatch /tmp/aes.o was compiled for kernel version 2.4.21pre4-6mdkBOOT while this kernel is version 2.2.19-BADZ5. extracting loop.o /tmp/loop.o: kernel-module version mismatch /tmp/loop.o was compiled for kernel version 2.4.21pre4-6mdkBOOT while this kernel is version 2.2.19-BADZ5. insmod loop failed at /sbin/modprobe line 35. I suppose that you could temporarily install an IDE drive into the machine and then bootstrap your way over to fixing the Mandrake image, but this is way too hard of a configuration to support. === Please support the aic_7xxx_old driver in both Cooker and the upcoming 9.1 release. === Thanks, and have a great day! Alvin
Re: [Cooker] aic7xxx_old installation problems
Pixel wrote: Alvin Austin [EMAIL PROTECTED] writes: PLEASE add the aic7xxx_old driver to the scsi host adapter list for expert mode. There are many, many machines out there that require this older driver. ok, adding (i don't know why it's not there already) can you give the output of lspcidrake -v | grep aic7xxx ? Here are three controllers that all require aic7xxx_old... aic7xxx : Adaptec|AHA-2940U/UW / AHA-39xx / AIC-7895 [STORAGE_SCSI] (vendor:9004 device:7895) aic7xxx : Adaptec|AHA-3940U/UW / AIC-7883U [STORAGE_SCSI] (vendor:9004 device:8378 subv:9004 subd:7883) aic7xxx : Adaptec|AIC-7815 RAID+Memory Controller IC [MEMORY_OTHER] (vendor:9004 device:7815 subv:9004 subd:7840) aic7xxx : Adaptec|AIC-7881U [STORAGE_SCSI] (vendor:9004 device:8178 subv:9004 subd:7881) Thanks for looking at this! Alvin
Re: [Cooker] aic7xxx_old installation problems
Buchan Milne wrote: On Sun, 16 Feb 2003, Alvin Austin wrote: Hi All, I'm trying to install the latest cooker onto a SCSI-only machine (even the CDROM is SCSI). The machine has an adaptec AIC-7895 host adaptor on the motherboard, which *requires* the aic7xxx_old driver. Unfortunately, this is not an option in expert mode (only the aic7xxx driver is given as an option). The machine hangs badly when the aic7xxx driver tries to load. AFAICR the aic7xxx_old is *only* necessary if you haven't updated your firmware. And, IIRC, all cards that used this driver can have their firware updated. The inclusion of the aic7xxx_old driver was only to tide people over while they got around to updating their firmware. But, I could be wrong, we only have 2 aic7xxx cards ... Buchan Unfortunately, Adaptec doesn't have updated bios drivers for many of their cards (the 2940UW is one, for instance, that I had flashed up to the 2.20 version of the bios, which is the latest on their site, but it still requires the aic7xxx_old driver). On another system with the controller onboard, the Adaptec drivers are part of the motherboard bios, and I haven't been able to locate an update to its bios either. I suspect this is a common dilemma. However, many of these are machines are fomerly NT servers and are finding new uses in the linux world, and we don't want this issue to be a stumbling block... Alvin
Re: [Cooker] kernel22 (was aic7xxx_old installation problems)
Guillaume Cottenceau wrote: Alvin Austin [EMAIL PROTECTED] writes: [...] Things go downhill with the other boot disks. - The hd-2.2.19-BADZ5 and the network-2.2.19-BADZ5 both let you install Mandrake, but don't install the aic7xxx_old driver into the initrd.img (the aic7xxx gets installed and then you can't boot). Installing with 2.2.19, it should install the kernel22 package, doesn't it boot? - If you try to use the 2.2.19 hd or network images in rescue mode (to try and run mkinitrd to add the aic7xxx_old driver), many modules don't load properly, because the /modules/modules.cz on these images is for the 2.4.* kernels not for 2.2.19. The worst thing is that the loop module cannot be loaded, which breaks mkinitrd. The error message is: Two solutions: - start with linux expert and load the loop.o module when prompted for a SCSI module, before the aic7xxx or - mount the CD, extract the loop.o module with packdrake from Mandrake/mdkinst/lib/modules.cz-2.2.19-BADZ5 and load it The kernel22 package is not in the current cooker tree, and the Mandrake Cooker (91B3) installation program gives an error that it can't be found near the end of the install session. Also, the module loading problem is more general. When you boot from the hd- or network-2.2.19-BADZ5 disks, *none* of the extra modules (ext3, loop, etc.) get loaded because of this bad version problem... A series of error messages flash by on the screen as these disks boot and the /etc/rc.sysinit script gets executed. It seems like the wrong version of the modules are packaged onto the image/alternative/*2.2.19-BADZ5* disks. Alvin
Re: [Cooker] kernel22 (was aic7xxx_old installation problems)
Guillaume Cottenceau wrote: Alvin Austin [EMAIL PROTECTED] writes: The kernel22 package is not in the current cooker tree, and the Mandrake Cooker (91B3) installation program gives an error that it can't be found near the end of the install session. Yep it's in the contrib. Also, the module loading problem is more general. When you boot from the hd- or network-2.2.19-BADZ5 disks, *none* of the extra modules (ext3, loop, etc.) get loaded because of this bad version problem... A series of error messages flash by on the screen as these disks boot and the /etc/rc.sysinit script gets executed. Yes, yes. It seems like the wrong version of the modules are packaged onto the image/alternative/*2.2.19-BADZ5* disks. No, the fact is that when the rescue starts, it loads module from the rescue, not the bootdisks. In the bootdisks, the modules are correct: you load your network/scsi drivers ok. The version of 2.2 kernel in cooker contribs is kernel22-2.2.20-9mdk.i586.rpm, so the modules from there is a mismatch between what the install wants (2.2.19) and what's there. Sorry, but I don't understand why booting an install floppy in rescue mode should try to load modules from some other version of the kernel other than what booted with the rescue itself. Common operations like mounting a vfat or ext3 partition fail because those modules can't load because of version mismatch problems. The shell mode prompt even tells the user to type modprobe module to load additional modules??? (sorry if I'm missing something that should be obvious here). You are correct that the scsi and network drivers get loaded properly, though. Alvin
[Cooker] postfix post-install bug
Hello Cookers, Here's a bug I noticed in a couple of recent 9.0 installations, so this might also be a problem in the current cooker (perhaps someone can check and report). In a full reformat and expert install, with the package postfix-1.1.11-4mdk installed, the post-install script does not set up the symbolic links to the sendmail binary for (at least) the 'newaliases' and 'mailq' commands. Easy fix afterwards on a running system is: cd /usr/bin ln -s ../../usr/sbin/sendmail.postfix /etc/alternatives/mta-newaliases ln -s ../../usr/sbin/sendmail.postfix /etc/alternatives/mta-mailq Then run the newaliases command. Merry Christmas to all, Alvin
[Cooker] Mdk9.0 and SMC WIRELESS - help please
Hello Mandrake friends, A bug, I don't know, but a question for sure... Is anyone successfully using Mandrake 8.x or 9.x with an SMC wireless network card (SMC2632W) and/or SMC access point (SMC2655W), especially with WEP keys enabled? Mandrake 9.0 RC2 (and several earlier versions also) detect the SMC2632W PCMCIA card and set it up nicely. I can get it to talk to the access point easily if (and only if) I do not set any encryption key in the /etc/sysconfig/network-scripts/ifup-eth1 config file. The moment I try to enter a key (and of course set the corresponding key on the AP, it is unable to associate. [The AP works fine against W2K laptops keyed similarly, or on this laptop if booted with W2K]). I have tried using a 10 character hex key for 64 bit WEP, like: WIRELESS_ENC_KEY=1122-3344-55 and a 26 character hex key for 128 bit WEP, like: WIRELESS_ENC_KEY=cf1c-54bb-5154-c9f2-86d9-9330-21 and a pass phrase key (with the AP set at 128 bit WEP), like WIRELESS_ENC_KEY=s:somepassword Nothing seems to work. Again, if I put in an empty arg like: WIRELESS_ENC_KEY= and turn off encryption on the AP, then the connection comes up immediately, and the card gets an IP address by DHCP from the main linux server on the lan, and works normally. /-\ All suggestions would be VERY MUCH appreciated! \-/ (And thanks to those who have put in all the hard work into MDK 9.0 so far. It is another winner!) More details, if you're still reading... :-) These are observed when it is working with no WEP key specified. The hardware: - Access Point: SMC2655W PCMCIA Card: SMC2632W HardDrake reports: -- Vendor: Intersil PRISM2 11 Mbps Wireless Adapter Description: Old device file: /dev/eth1 Module: wvlan_cs type: network dmesg reports: -- wvlan_cs: MAC address on eth1 is 00 04 e2 62 48 34 wvlan_cs: Unrecognised card, card return vendor = 0x0003, please report... wvlan_cs: Found firmware 0x8 (vendor 3) - Firmware capabilities : 0-0-0-0-0 /etc/sysconfig/network-scripts/ifcfg-eth1 - DEVICE=eth1 BOOTPROTO=dhcp ONBOOT=no IPADDR= NETMASK= IPXNETNUM_802_2= IPXPRIMARY_802_2=no IPXACTIVE_802_2=no IPXNETNUM_802_3= IPXPRIMARY_802_3=no IPXACTIVE_802_3=no IPXNETNUM_ETHERII= IPXPRIMARY_ETHERII=no IPXACTIVE_ETHERII=no IPXNETNUM_SNAP= IPXPRIMARY_SNAP=no IPXACTIVE_SNAP=no # WIRELESS_ENC_KEY=s:somepassword # WIRELESS_ENC_KEY=cf1c-54bb-5154-c9f2-86d9-9330-21 WIRELESS_ENC_KEY= WIRELESS_ESSID=SMC92475 WIRELESS_MODE=Managed WIRELESS_RATE=11M iwconfig eth1 IEEE 802.11-DS ESSID:SMC92475 Nickname:adell Mode:Managed Frequency:2.462GHz Access Point: 00:04:E2:62:48:34 Bit Rate=11Mb/s Tx-Power=15 dBm Sensitivity:1/3 RTS thr:off Fragment thr:off Encryption key:off Power Management:off Link Quality:92/92 Signal level:-11 dBm Noise level:-102 dBm Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:0 Missed beacon:0 ifconfig eth1 - eth1 Link encap:Ethernet HWaddr 00:04:E2:62:48:34 inet addr:192.168.1.10 Bcast:192.168.47.255 Mask:255.255.255.0 UP BROADCAST NOTRAILERS RUNNING MULTICAST MTU:1500 Metric:1 RX packets:313 errors:0 dropped:0 overruns:0 frame:0 TX packets:406 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:100 RX bytes:55838 (54.5 Kb) TX bytes:62532 (61.0 Kb) Interrupt:5 Base address:0x100 Thanks again for any and all help and suggestions! Alvin (aamc at crlogic.com)
[Cooker] 9.0B4 Bug Report - SoundBlaster Live
In 9.0B3 and 9.0B4, the SoundBlaster Live! soundcard support seems to be broken. This card worked fine in 9.0B1 and earlier releases of Mandrake Linux. In 9.0B3, the SB Live wasn't detected during installation. In 9.0B4, it is detected and installed, but no sound results. :-( sndconfig reports: Sound Configuration Utility 0.68 (C) 2000 Red Hat, Inc. PCI Probe Results - A PCI sound card was found in your system. The details are: Model: Creative Labs|SB Live! (audio) PCI Probe Results - The Creative Labs|SB Live! (audio) is not currently supported. It would be great if this could be fixed before the final release of 9.0. Thanks much! Alvin
