"Testing" Sensei & Sensei64
James C was saying something similar a lil earlier, he ended up getting the new kernel and the old kernel to work though. wonder what the issue was. but here's a screenshot of Sensei64 loading in virtualbox, on my Sensei64 host installationmeowcats wrote:Ok, but the 32bit PAE boots just fine with the same syslinux.cfg...
I actually tried booting the 64bit iso with grub4dos just now, and i got the same error message.
Loading the 64bit iso in virtualbox works though...
here's how my grub menu entry looks
title Sensei 64
root (hd0,0)
kernel /boot/Sensei64/vmlinuz root=/dev/sda1
initrd /boot/Sensei64/initrd.gz
and i have all the sfs files in /mnt/sda1/Sensei64
initrd.gz and vmlinuz is in /mnt/sda1/boot/Sensei64
- Attachments
-
- Sensei64VB.png
- (14.3 KiB) Downloaded 491 times
Ok I went and installed grub2, and put kernel in /boot/Sensei64, and sfs in /Sensei64.
/boot/grub/grub.cfg looks like
Boots and loads kernel, but still same error about not finding sensei64_001.sfs
/boot/grub/grub.cfg looks like
Code: Select all
menuentry "Sensei 64" {
set root=(hd0,1)
linux /boot/Sensei64/vmlinuz root=/dev/sda1
initrd /boot/Sensei64/initrd.gz
}
The high usage issue, can be replicated with stock.
Just open the task manager and check option "count cache as used". Free -m shows this number by default. Since its just cache, I wonder if its normal behavior then?
also md5:
Just open the task manager and check option "count cache as used". Free -m shows this number by default. Since its just cache, I wonder if its normal behavior then?
also md5:
Code: Select all
57207f5ad0a062b8e87dc64c77b09293 senapps64_001.sfs
82c8237cb92547017b09a0df10276f62 sendesk64-xfce_001.sfs
81ce9dd50c7a32b05ce4593b7b0283d0 sensei64_001.sfs
r u certain u're using that newer initrd.gz? can you check it to make sure the:
md5sum = 467776b53fe59ffab64c0f44e8d80bb8
it's working fine usb booting on my machine. it's loading the usb drivers correctly. I just fixed the kernel panic when using a save file too.
if it's not loading with that initrd.gz...then it's taking more than just ehci_hcd...or uhci_hcd to read your usb drive. finding out exactly which modules it takes to modprobe...to get your usb drive reading is not an easy task using the only method that i know of using. If I had that machine, and i was 'determined' to get it working with Sensei64...the procedure i would use would be:
Seeing if it usb boots with FatDog64-521, if so
rmmod ehci_hcd
rmmod uhci_hcd
rmmod ehci_pci
and so on....
until i got the usb drive to turn off. after identifying which module turns it on and off...that should be enough information to put in the init script...to get it to load the usb drive.
if it doesn't usb boot w/FatDog64-521....then that would lead to another massive mission of finding exactly which module needs to be loaded. i would next try a puppy other than FatDog64-521, that it does work on, to see if i can figure it out...and either compiling that module or having to recompile the kernel.
I only have these two computers with similar hardware, so presently unable to test it on a wide range of machines. as i come across different ones, and try usb booting Sensei64 on different ones....i may come across one that needs more than ehci_hcd, uhci_hcd, and ehci_pci...to be able to access the usb flash drive. I should then be able to pinpoint the issue and hopefully be able to resolve it.
md5sum = 467776b53fe59ffab64c0f44e8d80bb8
it's working fine usb booting on my machine. it's loading the usb drivers correctly. I just fixed the kernel panic when using a save file too.
if it's not loading with that initrd.gz...then it's taking more than just ehci_hcd...or uhci_hcd to read your usb drive. finding out exactly which modules it takes to modprobe...to get your usb drive reading is not an easy task using the only method that i know of using. If I had that machine, and i was 'determined' to get it working with Sensei64...the procedure i would use would be:
Seeing if it usb boots with FatDog64-521, if so
rmmod ehci_hcd
rmmod uhci_hcd
rmmod ehci_pci
and so on....
until i got the usb drive to turn off. after identifying which module turns it on and off...that should be enough information to put in the init script...to get it to load the usb drive.
if it doesn't usb boot w/FatDog64-521....then that would lead to another massive mission of finding exactly which module needs to be loaded. i would next try a puppy other than FatDog64-521, that it does work on, to see if i can figure it out...and either compiling that module or having to recompile the kernel.
I only have these two computers with similar hardware, so presently unable to test it on a wide range of machines. as i come across different ones, and try usb booting Sensei64 on different ones....i may come across one that needs more than ehci_hcd, uhci_hcd, and ehci_pci...to be able to access the usb flash drive. I should then be able to pinpoint the issue and hopefully be able to resolve it.
Yes the md5 match.
I have successfully managed to boot fatdog-521, no problems, same grub entry.
rmmod ehci_hcd successfully turns off my flash drive.
rmmod uhci_hcd seems to turn off my keyboard/mouse...
[edit]
in your initrd script I see
dashes instead of underscore. could this be why?
I have successfully managed to boot fatdog-521, no problems, same grub entry.
rmmod ehci_hcd successfully turns off my flash drive.
rmmod uhci_hcd seems to turn off my keyboard/mouse...
[edit]
in your initrd script I see
Code: Select all
modprobe usb-common
modprobe ehci-hcd
modprobe ehci-pci
no...that should be right, even with the dashes. try this...after loading and getting the sfs not found...from that prompt, type in
modprobe ehci_hcd...and see if u get an error.
does your flash drive have a light indicator of some sort to let u know that it's on....like how the sandisk flash drives are?
modprobe ehci_hcd...and see if u get an error.
does your flash drive have a light indicator of some sort to let u know that it's on....like how the sandisk flash drives are?
yea...it absolutely sounds like ehci/uhci_hcd aren't loading...that's why i'd like to see what modprobe says. hopefully u can give it a try with an old school keyboard?meowcats wrote:problem is, my keyboard and mouse are not working at ramdisk prompt either I would have to find an old OS/2 mouse/keyboard.
and the sfs files are placed on the flash drive...but still aren't being found...?meowcats wrote:Mouse/keyboard only work with the newer initrd you supplied.
With the old, mouse/keyboard lights are off; can not type anything at prompt
With the new, mouse/keyboard lights are on; able to type things!
there's no indicator light on either flash drive that shows rather it's on or not?