john3voltas wrote:nooby wrote:Suprising things is that Ubuntu obviously has changed how them set up things then because there it works?
Well, buntoo has an history of doing things the way they want without letting anyone else on it, don't they?
A budd of mine is a developer and sometimes he does minor fixes in their code.
Not long ago he told me that the release logs don't show even 10% of all the changes made into the code.
It's a bloody mess.
Even so, they usually do a hell of a job fixing the mess before it hits the streets...
Anyway, I can't write in the partition where grub4dos is installed but I can write in the partition where I have Pussy's vmlinuz+initrd.img+allsquashfs.
Maybe my difference is that I have grub4dos installed in a separate partition that win7 creates with just a 100MB. That's where win7 puts it's bootloader and that's where I have put grub4dos too.
Regarding my keyboard issue, it's not a Debian issue because I've just tested on my Debian Frugal and it worked properly.
Took a setxkbmap -print on Debian and it shows:
Code: Select all
user@debian:~$ setxkbmap -print
xkb_keymap {
xkb_keycodes { include "evdev+aliases(qwerty)" };
xkb_types { include "complete" };
xkb_compat { include "complete" };
xkb_symbols { include "pc+pt+inet(evdev)+level3(ralt_switch)+terminate(ctrl_alt_bksp)" };
xkb_geometry { include "pc(pc105)" };
};
user@debian:~$
Whereas a setxkbmap -print on puppy shows:
Code: Select all
sh-4.1# setxkbmap -print
xkb_keymap {
xkb_keycodes { include "xfree86+aliases(qwerty)" };
xkb_types { include "complete" };
xkb_compat { include "complete" };
xkb_symbols { include "pc/pc(pc102)+pc/pt" };
xkb_geometry { include "pc(pc102)" };
};
sh-4.1#
I wonder what I'll get in Pussy's setxkbmap -print.
Let me check that and I'll get back here to report it ASAP.
Cheers
@john3voltas
its quite possible that there are differences in the debian that you usually use and pussy due to a missing package or some such in pussy.
This fix from saintless seems to work:
apt-get install keyboards-rg
dpkg-reconfigure keyboard-configuration
in the next round of releases, pussy will have an entry in the catroll-panel that installs the keyboards-rg package then reconfigures it so you can then select your keyboard.
in regards to the writing to boot partition, once booted, open /etc/mtab and see if /live/image is mounted rw. Mostly unless your running ntfs the writing to boot partition just works but i have experienced some times when it doesnt. I narrowed it down to how grub boots it. I noticed that if i specified stuff like root=/dev/sda4/ etc etc that it didnt work, but if i didnt specify those things then it did work. Seems the less info in grub the better. If grub2 is installed on the same partition as pussy is installed on, you dont need to specify the root fs in grub2, it picks it up automatically.
Everything will work simply with:
menuentry 'Pussy'
{
linux /live/vmlinuz boot=live config swapon noprompt quickreboot noautologin
initrd /live/initrd.img
}
Or if you do need to specify the partition pussy resides on (ie grub is not installed on same partition as pussy)...then do it via the uuid like:
menuentry 'Pussy'
{
insmod part_msdos
insmod ext2
set root='(hd0,msdos1)'
search --no-floppy --fs-uuid --set 81b13c28-bddb-4ede-9edb-aee4159a93ba
linux /live/vmlinuz root=UUID=81b13c28-bddb-4ede-9edb-aee4159a93ba rw boot=live config swapon noprompt quickreboot noautologin
initrd /live/initrd.img
}
To find the uuid of a drive, pussy has a tool for that in the catroll-panel ---> filesystem ---->disk-uuid or you can use the blkid command.
there is something mysterious and magical about writing to the boot partition (ie. the live media). Mostly it works but when it doesnt its a bit of a puzzle, but the simpler the grub config the better. When i had this problem, i removed everything that didnt need to be in grub and it worked, but i dont know exactly what stops it working.
[EDIT] After testing i can confirm that this type of tag: root=/dev/sda4 rw
stops you having rw access and that is with and without the rw bit at the end.
Also, simply just specifying: set root='(hd0,1)'
this stops you having rw access aswell. I think you need to have the insmod bits in there if you need to specify a partition other than the one grub is installed on.