crazyspongebob

I think you should delete the line that automount the winXP partition in fstab file. I had the same problem when I warm reboot my box from Mandriva back into winXP. After giving the box a cold hard boot (turning the box off and on), I have no problem at all. J.T.

Post your hardware. There are quite a few scenarios that after installation Mandriva runs into kernel panic. J.T.

Have you tried Ubuntu 5.04? I was able to install it on a 2-month old compaq 64 R4000 laptop but unable to install 2005 LE. J.T.

That tip does not help me at all. It does not go into details. I was able to install 2005LE successfully after typing alt2 at the boot prompt but unable to boot completely from the usb drive. It went into kernel panic after init tried to mount root and boot partitions. I am more successful with 2006 RC2. I am able to install and boot 2006 RC2 from a system that can boot from usb to make a boot CD. Then I use that boot CD to use the usb drive in systems that cannot boot from usb. My usb drive is 40 gig WD Passport. J.T.

I had quite the similar problem with 32-bit 2005LE on my AMD64. Ubuntu 5.04 works fine. J.T.

Actually 2005LE will install in USB harddrive if you don't use the default kernel by hitting ENTER key at the boot screen. Type alt2 (kernel 2.6.8.1, it's the default kernel for 10.1) at boot prompt if I remember correctly. Even 2006 RC2 has the same problem. I have to use that alternative kernel to install 2006 RC2. I think Mandriva has an announcement regarding changing mandrake url to mandriva url for updates and package installation on www.mandrivalinux.com. J.T.

Have you tried the ndiswrapper to use windows driver? I used that on my laptop with 2006 RC2 and it works like a charm. J.T.

Hi jobanx, I wonder if you can lower the speed of burning those CD images. I don't know why Mandriva does not include CD integrity checking during the installation process like Fedora or Ubuntu so that you know if your burned CDs are good or not. Reburn those CD images. J.T.

Hi, I just installed 2006 RC2 on my usb hard drive during the weekend and had to choose the alt1 kernel which is the default kernel for 10.1(version 2.6.8.1 I think). I was able to boot from the usb drive this time. It's really weird that the same kernel throughout three version but one cannot recognize the drive (10.1), the other recognizes and installs but cannot boot(10.2), the last installs and boots (2006 RC2). However, there is a little quirk with X. When I log out, X hangs. I have to use CTR+ALT+Backspace to shutdown X. J.T.

I have tried both 10.1 and 10.2 installation without any trouble. However, booting from the drive is another story. It just frustrating when the older kernel is able to see the ext usb drive but not the newer kernel. I'll try ubuntu to see what happens. J.T.

I think the problem of LE2005 is the kernel. The default kernel for installation does not recognize the usb drive if you just hit ENTER at the boot prompt. After hitting F2, you enter alt2 (kernel version 2.6.8.1-12) as the boot option as the installation kernel, LE2005 recognizes the usb drive and installs without any problem. However, LE 2005 installs the default kernel (version 2.6.11) which does not recognize the usb drive. For me I don't know how to get kernel 2.6.8.1 to be the default booting kernel for my usb drive installation of LE2005. It's a bit strange that even though I choose the alternative kernel to install but LE 2005 installation still uses the other kernel as the installation kernel. I think 101. using 2.6.8.1 kernel is the reason why 10.1 works but not LE2005. J.T.

Hi Jim, I was able to install LE 2005 without a hitch several times using the alt2 option. However I was not able to boot that installation without a boot cd or floppy. I tried the installation on my brother AMD 64 laptop without a hitch. After the successful installation, I tried to boot and got kernel panic error since init could not mount the drive even though usb driver was loaded at boot. I don't know what to do to get it boot J.T.

Hi Jim, I was able to install LE2005 on a 40g usb drive, but unable to boot. I installed LE2005 by typing alt2 (kernel version 2.6.8.1 I believe) at the boot prompt. Somehow LE2005 does not recognize usb drive by the default kernel. I also don't know how to make a boot disk since my laptop is a prostar 1ghz usb1.1 with no usb boot. I have tried my usb drive with some latest hardware systems which support usb boot but I get kernel panic because init cannot mount the usb drive (/dev/sda). J.T.

You need a time server running NTP(network time protocol). Then on your client box (mandrake 10 and 10.1), open up mandrake control center. Go to System and then date and time. Check to enable network time protocol. Type in the server's ip address or name. However, before you can do all this, you have to install ntp on your client box. If you don't have a ntp server, there are good number of ntp servers on the net which you can choose from. J.T.

Have you tried to set up in text mode without mouse and Xwindows? You can choose the text mode at the boot up screen. J.T.

My system is up-to-date with all the latest patch. It's just that the box was working 2 days ago with no problem. As I said in the last message, I went into /etc/rc.d/rc5.d and removed to links related to sound scripts, and the system started fine. I found some odd entries in /var/log/messages regarding alsa. The following is part of /var/log/messages regarding alsa. Thanks Feb 20 14:41:54 laptop rc: Starting partmon: succeeded Feb 20 14:41:55 laptop kernel: PCI: Found IRQ 5 for device 0000:00:01.4 Feb 20 14:41:55 laptop kernel: PCI: Sharing IRQ 5 with 0000:00:0a.1 Feb 20 14:41:56 laptop alsa: succeeded Feb 20 14:41:53 laptop netplugd[2535]: /etc/netplug.d/netplug eth0 in -> pid 2535 Feb 20 14:41:53 laptop netplugd: netplugd startup succeeded Feb 20 14:41:59 laptop alsa: succeeded Feb 20 14:42:02 laptop sound: Loading mixer settings succeeded Feb 21 17:08:02 laptop netplugd[2501]: /etc/netplug.d/netplug eth0 in -> pid 2501 Feb 21 17:08:02 laptop netplugd: netplugd startup succeeded Feb 21 17:08:08 laptop alsa: succeeded Feb 21 17:08:10 laptop sound: Loading mixer settings succeeded Feb 21 20:52:39 laptop kernel: PCI: Found IRQ 5 for device 0000:00:01.4 Feb 21 20:52:39 laptop kernel: PCI: Sharing IRQ 5 with 0000:00:0a.1 Feb 21 20:52:40 laptop alsa: succeeded Feb 21 22:08:26 laptop kernel: AC'97 0 analog subsections not ready Feb 21 22:08:27 laptop alsa: succeeded Feb 21 22:11:39 laptop kernel: PCI: Found IRQ 5 for device 0000:00:01.4 Feb 21 22:11:39 laptop kernel: PCI: Sharing IRQ 5 with 0000:00:0a.1 Feb 21 22:11:40 laptop alsa: succeeded Feb 22 00:48:20 laptop kernel: MC'97 1 converters and GPIO not ready (0xf20d) Feb 22 00:48:21 laptop alsa: succeeded Feb 22 01:03:21 laptop kernel: PCI: Sharing IRQ 5 with 0000:00:0a.1 Feb 22 01:03:22 laptop alsa: succeeded Feb 22 14:54:10 laptop kernel: PCI: Sharing IRQ 5 with 0000:00:0a.1 Feb 22 14:54:11 laptop alsa: succeeded The above are /var/log/messages snippets since the whole file is too big to post here. My laptop has SIS 630 chipset and 7018 PCI audio. Now even after detecting the sound driver as snd-trident, draksound hangs. Update: I used harddrake to configure the soundcard in Xwindows. This time I use trident driver not snd-trident, and I have sound. However, the kmixer is no longer loading when I log into Xwindows. J.T.

I have a Prostar laptop with Mandrake 10 download version. Last night, when I turned my laptop on, it just hung at "Doing alsactl to restore mixer settings..." So I booted the laptop into failsafe mode and then went into /etc/rc.d/rc5.d/ to remove to scripts that started the soundcard. This made my computer have no sound. So, today I log in as root and run alsaconf to reconfigure the soundcard, and it just hangs at the above mentioned message. I had had sound before. The soundcard is as SIS with ALSA trident driver. any suggestion? J.T.

I think it is part of usb thing. When you plug in you usb drive Mandrake tries to detect and mount the drive automagically for you like in Window$. So you don't have to enter a line for usb drives in fstab and mtab. In mdk 10.0 and 10.1 CE, the auto-detection and auto-mounting work fine in my case. But in 10.1, I am having a little headache. Even though mdk 10.1 harddrake detects the drive as sda, but it does not auto-mount the drive. I have to run the configure tool to mount, but it does not work after a reboot. I have turned on hotplug for usb and firewire devices, but it still doesn't work properly. J.T.

I have tried it, but it does not work. Actually it worked for one reboot. Afterward, mdk 10.1 detects the drive as sda but does not mount it. It's a bit frustrating. J.T.

I'll try to enable hotplug to see if my QuickiDrive be mounted automagically for any user on the box. Thanks J.T.

I used mdk 10.0 official and 10.1 CE. Both do a good job at automagically mounting my usb flash memory drive like window$ does. However, two days ago, I switched my box to mdk 10.1 official with a clean install. Now, the auto mounting is no longer working. I have to use harddrake to mount it. I also have to use expert mode and use options to mount for the relgular users to write to it, unlike to 10.0 and 10.1 CE. How can such a difference be between version? Do I have to enable anything like hotplug or harddrake for it this to work? I remember to turn of those two services and the automount still work in 10.0 and 10.1 CE. J.T.

I installed mdk 10.1 CE and used it for a while without any problem with the CD drives at all. Two days ago, after having probems with burning the mdk 10.1 official iso's on to CDs, I installed it and began having the same CD drive lock-ups problem with the same dialog box appearing on the screen. Any ideas? J.T.

I have tried to burn the iso's at different speeds but no use. I still get errors at the second CD. Now I have 4 sets of no good CDs and one DVD. I had no problem with 10.1 CE or 10.0 at all. J.T.

I havd had the same problem. I have wasted 3 sets of CD-R burned off on both a linux box and windows box. In my case, it just happens to the second CD. J.T.

I wonder if you have a fully qualified domain name. Check you /etc/hosts file and /etc/sysconfig/network file to see if your hostname is there. The hostname in those two places has to be the same. It is just a suggestion. Somehow, when you lose network connection and your box is on DHCP, it cannot pull the the domain name. J.T.