3.4 issues - mysql, usb, kolf, grub
Posts: 11
Hopefully this is the right forum, hard to tell with so many of them. I did an install of 3.4 rc1 from the CD, then copied over my home directory files from my 3.3 partition. Problems:
1) I added apache2, php and mysql through synaptic. Apache and php seem to be working, but mysql isn't, just says it can't connect to server. Packages installed: libmysqlclient14, libmysqlclient15, mysql-client-5.0, mysql-common, mysql-server-5.0, php5-mysql
2) My USB key (SD card reader actually, same difference) which was working fine on 3.3 (though perhaps I'd customized something and forgot) no longer works. The 'devices' spot in konqueror where i used to aceess it simply says "protocal not supported" when clicked. It adds a "removable device" icon to the desktop, which gives this output:
mount: block device /dev/sda1 is write-protected, mounting read-only
mount: wrong fs type, bad option, bad superblock on /dev/sda1,
missing codepage or other error
In some cases useful info is found in syslog - try
dmesg | tail or so
3) I also added Kolf through synaptic. When I try to run it, it simply quits. It'd be a shame if I didn't have a chance to beat my 44 on the hard course.
4) Finally, despite installing on another partition, I let grub reinstall and so in grub's usual blind way it doesn't provide access to let me boot mepis 3.3. I've attempted editing menu.lst but with no luck at all (I can get the option listed, but it doesn't work). Here's the stanza that doesn't work:
title MEPIS at hda4, kernel 2.6.10
kernel (hd5,3)/boot/vmlinuz-2.6.10 root=/dev/hda4 nomce quiet splash=verbose vga=791
initrd (hd5,3)/boot/initrd.splash
I'm sure hda4 is right, but have no idea what I'm doing with the rest. At least if I could fix grub I could boot to the working mepis and get some work done.
for grub
Posts: 1504
where it say's "(hd5,3)" ,do you have 5 hard drives? #1 hd=(hd0.3) #2 hd=(hd1,3)
So since your on hda4->
title MEPIS at hda4, kernel 2.6.10
kernel (hd0,3)/boot/vmlinuz-2.6.10 root=/dev/hda4 nomce quiet splash=verbose vga=791
initrd (hd0,3)/boot/initrd.splash
Re: 3.4 issues - mysql, usb, kolf, grub
Posts: 11
Jon - My MySQL problem turned out to be much simpler than that -- I was too stupid to figure out to start it running. Now that I've run mysqld in konsole it's working. Was expecting it to autostart on booting... will have to find the option for that.
kerry - Works, thanks. As you can tell I had no idea what the number meant, hopefully I'll remember now.
As far as USB goes, got that fixed with some help.
Making Progress!
Posts: 5513
Well Hoth, it sounds like you're making good progress.
As to the autostarting, you can open a konsole and see if you have the links to the startup script that's located in /etc/init.d/mysql. Enter the following command, and you should see similar results:
ls -lad /etc/rc*d/S*mysql # That's an uppercase letter "es" lrwxrwxrwx 1 root root 15 2005-06-09 22:08 /etc/rc2.d/S20mysql -> ../init.d/mysql lrwxrwxrwx 1 root root 15 2005-06-09 22:08 /etc/rc3.d/S20mysql -> ../init.d/mysql lrwxrwxrwx 1 root root 15 2005-06-09 22:08 /etc/rc4.d/S20mysql -> ../init.d/mysql lrwxrwxrwx 1 root root 15 2005-06-09 22:08 /etc/rc5.d/S20mysql -> ../init.d/mysql $
Let me know if you have these links. If they are missing and you do not know how to create them, post back and I can give you instructions 
Jon
MySQL Issues
Posts: 5513
Hoth, I can't comment on all of your issues, but I have a couple suggestions for MySQL.
First, prior to your copying the data from your old system or disk, did mysql exist at all? If so, did you shut it down properly? Open a Konsole, "su" to user root, enter the command "/etc/init.d/mysql stop". Also, what prior version of mysql were you using?
I noticed that you installed mysql-5.0 on your new system. There appear to be some "issues" with conversion from 4.1 to 5.0. I'm not an expert on mysql, but I had a similar issue during testing. What I would suggest as the real first step from shutting down mysql above is performing a "mysqldump". This can be done from the command line as:
To reload the data into the new database:
Jon