kfoss

No, in this case it is an input module that needs to be put in the /usr/X11/lib/modules/input directory.

I have a quck question on some post-kernel installation actions. I have s touch screen display that I have working with the old kernel. The "evtouch.o" file is in the X11 input module directory. I know I can rebuild the file for the new kernel but it will then make it unusble for the old kernel. How can I set this up for a two kernel boot option?

The new kernel was added but this did not change the problems with the USB Wireless LAN devices crashing. I am going to attempt a manual kernel update and see where that take me.

I found the kernel update problem. The kernel that is being used after the install is the 2.6.12-12mdk-i586-up-1GB. The up-1GB makes a difference. I urpmi'd the -24mdk-i586-up-1GB and it finally worked!!!

All, Actually, I did exactly what was recommended. I used the "urpmi kernel-2.6.12.24.mdk". It downloaded, installed and did a LILO change. I proceeded to reboot, why question the packagers? Well I should have. The kernel installation modified the symlinks in the /boot directory so that vmlinuz pointed to the newest vmlinuz-2.6.12-24mdk file and left the old 2.6.12-12mdk.i586... file alone. All the other symlinks were modified as well. Now I was never able to restart. After using a rescue distro, I found that the lilo.conf file was not modified properly to match the changes to the /boot directory. At this point I personally had not done any modifications to anything. In the lilo.conf file, the new -24mdk was added but the kernel and initrd image it was pointing to were not the vmlinuz and initrd.img links, but the actual -24mdk files. This should have still worked if I chose the -24mdk boot option, it didn't. What was worse, was that it left the original -12mdk to the symlinks, which in the background were all the new -24mdk files. By rights if the install worked, choosing the default -12mdk or the new -24mdk option from the boot menu should get me a -24mdk-based OS. Neither worked. So when I say I modified the lilo.conf, it was to allow me to boot back into the original -12mdk system, which it does now. The -24mdk system doesn't work. Just for your knowledge, I also tried the -23mdk version and I get the same result as the -24mdk version. Now on the subject of the Wireless USB devices. Thanks for all the links, but it's not the hardware, which is why I put the post in the software section, since it is a kernel problem IMHO. I've been using the AirLink USB devices for over a year now, and currently have one running with the ZyDas ZD1211 drivers on my HTPC (using Mandriva 2006.0!). I've swapped them out and they both work fine on the HTPC system. I've also tried the DLink dongle and built the RT2570 drivers, which seem to work, but the moment the device tries to Tx/Rx the system freezes. This is the same thing that happens with the ZyDas based USB device. So this tells me it's the OS, not the hardware, nor the drivers. I've been through the BIOS and made all the recommended changes too. The only thing I haven't done is the kernel update, since it isn't working. Any ideas on why the kernel update isn't working using urpmi? My next step would be to try a kernel upgrade to something similar to the pclinuxos kernel (2.6.17) by doing a manual kernel build. Once again, even when following all the guides, I've never has a kernel build and upgrade work properly.

All, I've tried all the recommended courses of action, the BIOS changes has no effect or were already set. I also did the kernel update. I modified the lilo.conf file after the update and when I try to boot the new 2.6.12-24mdk kernel, the system does an automatic reboot. The current kernel still works. Either something is wrong with the kernel update process or the directions given on the Mandriva site are wrong.

pmpatrick, During my troubleshooting efforts last night, one of the last things I did was to enter the update locations in urpmi. However, I felt it too late to attempt a kernel update safely, even though it seems relatively benign. I will attempt the PnP verification in the BIOS first, then the update.

So what could be happening is that when I connect a device or "make it active", I'm running out of IRQs or losing the IRQ associated with the original device attached? Thanks again, I learned something new today!

Tyme, I will check it, but if this was the issue, wouldn't I have had a similar problem between the 9.2-based install and the 2006.0-based install? The BIOS has not changed since the original build.

I will check that the moment I get home. Thx.

Hi, I've been working to build a CarPC and have ran into some speedbumps, though not the literal ones. I started the project by using PCLinuxOS 0.93 MiniMe, since it was small and was Mandrake 9.2-based. I had the whole system running when I found a new Navigation application, RoadNav. Unfortunately, RoadNav requires libstdc++.so.6 and I only had libstdc++.so.5. So I upgraded. I made a fresh install of Mandriva 2006.0 which I also have running on my main PC and my HTPC, both running smoothly. The CarPC system consists of: 1. ECS C3VCM2 MITX motherboard (similar to a Epia 800MHz board) 2. Lilliput 7" 619GL Touchscreen LCD 3. Pharaos 360 USB GPS 4. Integrated CastleRock graphics with XvMC acceleration enabled and working with MPlayer My problem is that any time I try to add a Wireless LAN - USB device, my system hangs, crashes or I lose one of the other USB devices. I have tried to use three different WiFi devices (Netgear WG111, Airlink AWLL3026 & DLink DWL-G122) and all cause similar problems. With APCI=on and APIC enabled, when the wireless devices try to become active, the whole system freezes. I have checked the /var/log/messages and there is nothing, just some messages about the USB device connecting and then the next message is the "restart" line. With APCI=off and NOAPIC in LILO, at least the system doesn't hang when the device becomes active. An example of what it does is that when I reboot with the WiFi plugged in and configured, the touchscreen's USB interface no longer works. If the Wifi adapter is not plugged in and I reboot, the touchscreen works fine. When I then plug in the Wifi adapter, the USB GPS interface can't be found by the Nav application, even though the GPS driver and "gpsd" are running. It's confusing since all these devices worked on a Mdk9.2 based system, but 2006.0 doesn't. It's not the hardware that's failing, it's the OS. Where should I start looking correct this problem? Any ideas? [moved from Software by spinynorman]

I've been running 2006 Official for a couple of months now and have been very happy. I had upgraded my mobo and therefore took advantage of the situation and upgraded everything. I have also recently purchased my first MITX system and have also install 2006. Everything is working fine but the only issue in both cases is the sensors modules. For my Gigabyte K8N51PVMT-9 the modules is the WinBond 83627ehf and on the EPIA it the vt1211. In both cases the modules are not in the default kernel, but they are available in some form in later kernels. I've never been a fan of updating kernels for a single fix, but in this case it'll fix two systems. Normal kernel updates for the default kernel are not enough as I need to get to 2.6.15 or greater. Any recommendations on how to accomplish this with Mandriva 2006 without killing my system. During my Linux Life, I'm batting Zero for kernel updates.

I've recently forced myself to upgrade from 10.0 to 2005LE. In 10.0 I have each of my three desktops with its own background. As well my menu had the most recently used applications. I've been through the KDE setup and cannot find how to do this now. Any help?

John, Yes, I have actually looked at MCC at I know that my drive is listed as /dev/sr0. This is due to the fact the in LILO I have to have hdc=ide-scsi in order to make my burner burn. Otherwise it's just a slightly more expensive DVD-ROM. This is one of the problems with the 2.6.3xxx kernel, that you need ide-scsi emulation to make burners work. I have tried to update my kernel as well. The stock kernel for 10.0 is 2.6.3-7mdk. The Mandrake update downloaded 2.6.3-27mdk. Just to ensure that all was koshier, I compiled and installed the -27mdk version. No matter what I did, reboots, re-configs, I could never get my keyboard and mouse to work again. So I left the -7mdk as the default in LILO and here I am. Eventually I will upgrade to Mandriva2005(10.2) and hopefully the new bugs that are introduced will not affect me. I will likely dualboot 10.0 and 10.2 until I have all of my current config working on 10.2.

John, Thanks, my drive is a Pioneer DVR-A05 which is an old 4xDVD-R(W) drive. I know that in some cases it is good to have an autoplay or auto-'whatever' capability. However, at this point, I want to remove the function as it happens whenever I insert a blank disk. It knows I want to burn. But once one of these programs starts, the ide-scsi module is corrupted. At this point I know that this is a known problem in the 2.6.3 kernel. I know that upgrading to 10.1/10.2 would get rid of this problem, but I'm not ready to do this yet. My system is exact the way I want it and is as stable as I have ever had it, except this ide-scsi thing. Someone has to know how to set this option of autostarting. It wasn't in earlier version of Mandrake like 8.0, or 9.0/9.2.

I am currently running the stock 2-6-3-7mdk kernel for MDK 10.0. I have applied all the updates thus far, but have not yet migrated to 10.1 or 10.2. At this point I would find it useful to just be able to turn off the autoplay feature for the DVD -RW drive.

Hi, I have narrowed my problem down to that when I insert a blank disk (cd-r or dvd-r(w)) into my Pioneer DVR105, the default burning program starts up. After this happens, if I try to burn something, I get a kernel error in ide-scsi. This occurred with K3B and the one with Konqueror. If the disc is in and I reboot, the burning is fine. How do I turn off the autostart of a burning program when a disc is entered? Kevin

Thanks, I know that the BIOS recognizes the 160GB, as I am able to see it in the BIOS SATA listing as 160GB, thouh this is probably the BIOS reading from some data stored on the drive's circuits. I am, in MDK10.0 able to see the drive in the partition manager and it says 160GB. PMPatrick, you are riight though. I actually have a Western Digital SATA, not Maxtor drive. I also have another ATA100 160GB by WD and when I look at it's drive capacity, you got it...it only adds up to 146GB just like to new one. So my question now is, if I buy a 200GB or larger HDD, will I need to split it up into partitions or will MDK 10.0 and my Asus A8V (current generation AMD64 board) let me keep is a one large partition? Ideas? Thanks for all the input so far!

I have recently installed a Maxtor 160GB SATA HDD and created a 10GB system partition and a 150GB partition for saving recorded TV shows. The 150GB partition only shows as 136GB after being created and formatted. Is there still a 136GB limited to harddrives in Linux? Missing 14GB is pretty significant...10%+ of the capacity... Ideas? Kevin

Good Day, I have been using a Backpack CDROM connected to the parallel port. Under MDK 9.2 I coiuld mount it under /dev/pcd0. Now under MDK 10.0 I cannot. The /dev/pcd0 device did not exist do I created it with mknod. The /dev/pcd0 directory has two subdirectories ataraid and something like cccsi. Anyways, it used to work under 9.2 but not under 10 so something with devices have chaged. I insert the paride, bpck and pcd modules as per normal and everything looks fine under dmesg. Any ideas what I;m doing wrong? Kevin

I am looking for a good application that can import MPEG or DIVX files for editing. Most that I have found including kino, kdenlive, cinelerra, jahshaka, are all specific to special formats. I have already captured most in DIVX or MPEG format and want to put them together into a video. I would be willing to capture to raw or DV format but I am using a composite-in as I don't have a firewire camera. Any recommendation on editing or capture apps. I am using a WinTV card on Mandrake 9.2. Thanks.

Whenever I read these kind of "I'm building a new system..." posts I always get the urge to upgrade/build a new system myself. I also noticed that a lot of people are changing their views on the priority between cooling and noise. It wasn't long ago when everyone said "cool, cool, cool". Now, increased importance is being placed on the quietness of the system. My current upgrade plan is only for quietness. I am running an XP2000+ on an ECS K7S5A Pro and have been really happy. I added a couple of case fans about a year ago for cooling but now find I want more quiet. So I am looking at replacing my OEM HSF with a Scythe Kamakaze (it fits on the MoBo) and putting my HDDs in silent enclosures. My cases fans will be replaced with Silent/Ultraquiet Zalman Fans and fan controllers, and all my IDE cables will be replaced with round cables. Does anyone have other methods of reducing noise in their system?

Can anyone help me setup running a Redhat/Fedora first boot script after the installation of Mandrake. I have built a system for an in-law and most of the questions in the Mandrake setup are during the install. I would like for them to enter/re-enter specific information after they get the computer. It, of course, would only run once and then not run again.

A quick question to ask if anyone is running Mdk 10 and has also gotten Gatos to run. Gatos, in my case meaning having the 'km' capture drivers and the 'avview' application compile and run. I currently have all running under Mdk 9.2 exactly the way I want, but have been known in the past to run a couple of versions of Mdk old just to ensure that my ATI AIW card worked with Mdk. If others have had success I would be will to upgrade to Mdk 10, but don't want to mess up a 'well oiled machine'! Thanks.

It really depends on the size of your network. I have a similar setup and for all of our PCs I give them static addresses. My wireless access point/router gives any wireless devices a dynamic address using DHCP. A small network using up to a dozen IPs is easily handled using static IPs, so IMHO using DHCP is not very useful. Accessing shares through SMB needs to have static IPs as Samba likely uses the /etc/hosts file or similar which all links a static IP to a hostname.