gc-linux-devel — Development-related discussion.

Re: [Gc-linux-devel] ide-scsi problem

[Pierre S. <mug...@ya...>]

I'll definitively give it a try this weekend

I've got a couple of last minute dumb questions...

1) I know the tutorial says to produce it using a Linux PC, is it possible to follow it on my linux wii? If not, is it possible to follow it using a linux Live CD (such as Ubuntu)?

2) Can I apply mike's patch to versions 2.6.32 on? I'll do it on the 2.6.32, but it'll be cool to have it on the last stable version 2.6.36

I'll let you know how it went next week

Cheers and thanks again!

Pierre Sellamastique <mugre1975 <at> yahoo.com> writes:
> By "building a kernel" do you mean recompile the kernel?

Yes.

> If so, I've no idea how to do that (I told you I'm really new at this!), I 
know I need the source kernel (2.6.32 in
> this case), and then I guess I could follow one of the thousands tutorials or 
"how to's" on the web.
> 
> Still, I don't know if it comes with preloaded options and you just modify the 
ones you want (case in point,
> the one you're telling me), or if you need to know all the options there is to 
configure from scratch.
> Anyway if you could point me to the source kernel and a tutorial or "how to" 
to recompile it, I'll give it a try gladly!
> 

Sure.

Start with the kernel configuration of your actual kernel image. To get your 
kernel configuration just boot into your whiite linux installation and do a 
"zcat /proc/config.gz > /tmp/my_kernel_config.txt". This will create a file 
named /tmp/my_kernel_config.txt, which you need to copy to your "build" machine 
(i.e. where you will build/compile your kernel).

Then follow the instructions at:

http://www.gc-linux.org/wiki/Building_a_GameCube_Linux_Kernel

At step 2 of "Building the kernel image", instead of using a default config, do 
copy the contents of your my_kernel_config.txt file to linux-2.6.32/.config . 
Then modify the .config file to set the needed option (CONFIG_BLK_DEV_SR=y). The 
.config file is a text file that you can manually edit. Alternatively, if you 
prefer it, you can do a "make menuconfig" to tweak the options.

Cheers,
Albert



      

Re: [Gc-linux-devel] ide-scsi problem

[Albert H. <alb...@ya...>]

Pierre Sellamastique <mugre1975 <at> yahoo.com> writes:
> By "building a kernel" do you mean recompile the kernel?

Yes.

> If so, I've no idea how to do that (I told you I'm really new at this!), I 
know I need the source kernel (2.6.32 in
> this case), and then I guess I could follow one of the thousands tutorials or 
"how to's" on the web.
> 
> Still, I don't know if it comes with preloaded options and you just modify the 
ones you want (case in point,
> the one you're telling me), or if you need to know all the options there is to 
configure from scratch.
> Anyway if you could point me to the source kernel and a tutorial or "how to" 
to recompile it, I'll give it a try gladly!
> 

Sure.

Start with the kernel configuration of your actual kernel image. To get your 
kernel configuration just boot into your whiite linux installation and do a 
"zcat /proc/config.gz > /tmp/my_kernel_config.txt". This will create a file 
named /tmp/my_kernel_config.txt, which you need to copy to your "build" machine 
(i.e. where you will build/compile your kernel).

Then follow the instructions at:

http://www.gc-linux.org/wiki/Building_a_GameCube_Linux_Kernel

At step 2 of "Building the kernel image", instead of using a default config, do 
copy the contents of your my_kernel_config.txt file to linux-2.6.32/.config . 
Then modify the .config file to set the needed option (CONFIG_BLK_DEV_SR=y). The 
.config file is a text file that you can manually edit. Alternatively, if you 
prefer it, you can do a "make menuconfig" to tweak the options.

Cheers,
Albert

Re: [Gc-linux-devel] ide-scsi problem

[Pierre S. <mug...@ya...>]

Fair enough, I'm not the first one then :)

By "building a kernel" do you mean recompile the kernel?
If so, I've no idea how to do that (I told you I'm really new at this!), I know I need the source kernel (2.6.32 in this case), and then I guess I could follow one of the thousands tutorials or "how to's" on the web.

Still, I don't know if it comes with preloaded options and you just modify the ones you want (case in point, the one you're telling me), or if you need to know all the options there is to configure from scratch.
Anyway if you could point me to the source kernel and a tutorial or "how to" to recompile it, I'll give it a try gladly!

If I succeed, I promise to post the recompiled version on a fileserver for newbies generations to come...

Thanks a lot for your reply, and patience!!!


      Re: [Gc-linux-devel] ide-scsi problem
      From: Albert Herranz <albert_herranz@ya...> - 2010-10-21 18:09

      Pierre Sellamastique <mugre1975 <at> yahoo.com> writes:

      > 
      > Hi everyone
      > 

      Hi,

      > I seem to be having a problem no one had before.
      > 

      Guess not :)

      > I'm running the latest version of whiite on my wii, with a Fluxbox desktop, 
      and this last few days I've been
      > trying to workaround DVD playback capability using xine-ui and an external USB 
      DVD recorder (Samsung),
      > which seems to be SCSI.
      > Anyway, I know by now that I should create a link that makes /dev/scd0 point 
      to /dev/dvd to make it work, the
      > problem is I can't mount the USB device.
      > 
      > I've been reading lots of forums and by now I think the problem is: there's no 
      ide-scsi module on my
      > distribution, I couldn't find it, and furthermore there's no reference to it 
      in my /etc/modules.conf
      > file, plus when I run "modprobe ide-scsi" the system confirms there's no such 
      module.
      > 
      > My question: Is there a way to get that module? Or any other way to mount the 
      DVD disc on my USB device?
      > 

      Try building a kernel with CONFIG_BLK_DEV_SR=y.
      The stock gc-linux kernel comes without support for "normal" optical drives.

      > I'm kinda of a newbie in linux trying to learn as fast as I can so try to put 
      up with me
      > 
      > Thanks
      > 

      Your welcome.

      Cheers,
      Albert




      

Re: [Gc-linux-devel] ide-scsi problem

[Albert H. <alb...@ya...>]

Pierre Sellamastique <mugre1975 <at> yahoo.com> writes:

> 
> Hi everyone
> 

Hi,

> I seem to be having a problem no one had before.
> 

Guess not :)

> I'm running the latest version of whiite on my wii, with a Fluxbox desktop, 
and this last few days I've been
> trying to workaround DVD playback capability using xine-ui and an external USB 
DVD recorder (Samsung),
> which seems to be SCSI.
> Anyway, I know by now that I should create a link that makes /dev/scd0 point 
to /dev/dvd to make it work, the
> problem is I can't mount the USB device.
> 
> I've been reading lots of forums and by now I think the problem is: there's no 
ide-scsi module on my
> distribution, I couldn't find it, and furthermore there's no reference to it 
in my /etc/modules.conf
> file, plus when I run "modprobe ide-scsi" the system confirms there's no such 
module.
> 
> My question: Is there a way to get that module? Or any other way to mount the 
DVD disc on my USB device?
> 

Try building a kernel with CONFIG_BLK_DEV_SR=y.
The stock gc-linux kernel comes without support for "normal" optical drives.

> I'm kinda of a newbie in linux trying to learn as fast as I can so try to put 
up with me
> 
> Thanks
> 

Your welcome.

Cheers,
Albert

[Gc-linux-devel] ide-scsi problem

[Pierre S. <mug...@ya...>]

Hi everyone

I seem to be having a problem no one had before.

I'm running the latest version of whiite on my wii, with a Fluxbox desktop, and this last few days I've been trying to workaround DVD playback capability using xine-ui and an external USB DVD recorder (Samsung), which seems to be SCSI.
Anyway, I know by now that I should create a link that makes /dev/scd0 point to /dev/dvd to make it work, the problem is I can't mount the USB device.

I've been reading lots of forums and by now I think the problem is: there's no ide-scsi module on my distribution, I couldn't find it, and furthermore there's no reference to it in my /etc/modules.conf file, plus when I run "modprobe ide-scsi" the system confirms there's no such module.

My question: Is there a way to get that module? Or any other way to mount the DVD disc on my USB device?

I'm kinda of a newbie in linux trying to learn as fast as I can so try to put up with me

Thanks


      

Re: [Gc-linux-devel] Wifi problems with whiite-linux

[Brad N. <big...@gm...>]

I had the same problem and couldn't solve it without replacing my old
linksys B-only router with a newer G one that can run dd-wrt.  It
still doesn't play very nice on the wireless network, causing some
problems for other adapters when wii linux is active.

Re: [Gc-linux-devel] Wifi problems with whiite-linux

[Alec W. <al...@gm...>]

Quick update: I've found a workaround. If I have it constantly pinging my
router (ie have ping as an init script), it doesnt disconnect (although it
can slow down at times). So it seems it must have been disconnecting because
of inactivity. Is there any way to disable that?

On 13 June 2010 10:52, Alec Wright <al...@gm...> wrote:

> Hi there, I've been having some really odd problems with the wifi on my
> wii. I'm using debian lenny with the whiite isobel kernel, and while my
> wireless connects fine, it seems to progressively die over the course of
> about 2-5 minutes. When i first boot it up, it works fine. I can ssh in and
> it works normally, with no significant delay. But after a couple of minutes,
> ssh starts getting laggy (i type something and it takes a few seconds to
> respond) before eventually freezing altogether. At this point it stops
> responding to pings too. This happened when it was literally a metre away
> for the access point. Oddly enough, when i moved it about 15 metres away, it
> worked for longer before the wireless locked up, but it still happened
> eventually. I thought it could be some sort of memory issue, with the wii
> only having 64MB RAM, so I plugged a flash drive into the usb port with a
> swap partition and swapon'ed it. Didn't help though. Wifi's fairly critical
> to my application, since I was hoping to plug a hard drive into the USB port
> and use it as a NAS sort of thing.
> Has anyone else had this problem? Or know where I can start with resolving
> it?
>
> Thanks for your time, and for all the great work the developers have done
> so far with porting linux to this console :)
>

[Gc-linux-devel] Wifi problems with whiite-linux

[Alec W. <al...@gm...>]

Hi there, I've been having some really odd problems with the wifi on my wii.
I'm using debian lenny with the whiite isobel kernel, and while my wireless
connects fine, it seems to progressively die over the course of about 2-5
minutes. When i first boot it up, it works fine. I can ssh in and it works
normally, with no significant delay. But after a couple of minutes, ssh
starts getting laggy (i type something and it takes a few seconds to
respond) before eventually freezing altogether. At this point it stops
responding to pings too. This happened when it was literally a metre away
for the access point. Oddly enough, when i moved it about 15 metres away, it
worked for longer before the wireless locked up, but it still happened
eventually. I thought it could be some sort of memory issue, with the wii
only having 64MB RAM, so I plugged a flash drive into the usb port with a
swap partition and swapon'ed it. Didn't help though. Wifi's fairly critical
to my application, since I was hoping to plug a hard drive into the USB port
and use it as a NAS sort of thing.
Has anyone else had this problem? Or know where I can start with resolving
it?

Thanks for your time, and for all the great work the developers have done so
far with porting linux to this console :)

Re: [Gc-linux-devel] USB keyboard not working

[Alexander G. <ag...@su...>]

Albert Herranz wrote:
>>> I just need to get back to 
>>> development and have a name for the new branch series :)
>>>       
>> Yes, please! 
>> That would be awesome. Any idea on how long it'd take you to do that? Anything I 
>> can do to 
>> help?
>>     
>
> I probably will give it a go during the weekend.
> If you have a list of drivers that you'd like to have ready first, just tell.
>   

Oh thanks a lot! I'm mostly interested in EHCI, wifi and the frame buffer.

But then again I'll be leaving for 2 weeks of vacation on Saturday, so
it's not really urgent anymore :). I'll get back to things after that
hopefully.

Thanks again,


Alex

Re: [Gc-linux-devel] USB keyboard not working

[Albert H. <alb...@ya...>]

>> I just need to get back to 
>> development and have a name for the new branch series :)
>
> Yes, please! 
> That would be awesome. Any idea on how long it'd take you to do that? Anything I 
> can do to 
> help?

I probably will give it a go during the weekend.
If you have a list of drivers that you'd like to have ready first, just tell.

Thanks,
Albert



      

Re: [Gc-linux-devel] USB keyboard not working

[Alexander G. <ag...@su...>]

On 21.04.2010, at 23:26, Albert Herranz wrote:

>> Would you mind 
>> to take a few minutes to get your master branch rebased against the current tip? 
>> :-)
> 
> 
> The MIKE series and mainline both now include gamecube and wii support, but they are now different code bases (mainline uses a different device tree and includes all changes resulting from the mainline review process of the merged parts).
> Instead of simply rebasing, my plan is to add back all non-IOS driver stuff to a mainline-based branch as I said.
> 
> I just need to get back to development and have a name for the new branch series :)

Yes, please! That would be awesome. Any idea on how long it'd take you to do that? Anything I can do to help?


Alex

Re: [Gc-linux-devel] USB keyboard not working

[Albert H. <alb...@ya...>]

> Would you mind 
> to take a few minutes to get your master branch rebased against the current tip? 
> :-)


The MIKE series and mainline both now include gamecube and wii support, but they are now different code bases (mainline uses a different device tree and includes all changes resulting from the mainline review process of the merged parts).
Instead of simply rebasing, my plan is to add back all non-IOS driver stuff to a mainline-based branch as I said.

I just need to get back to development and have a name for the new branch series :)

> KVM works just fine on the Wii btw - I booted a VM perfectly fine. 
> The major issue was swapping being seriously slow though, as the swap was on 
> OHCI.

Nice :)

Cheers,
Albert



      

Re: [Gc-linux-devel] USB keyboard not working

[Alexander G. <ag...@su...>]

On 21.04.2010, at 22:50, Albert Herranz wrote:

>> Btw - I have more odd USB results:
>> 
>> I figured I'd move my 
>> root fs from the SD card to a USB drive to speed up things a bit. Hence the try 
>> with EHCI. So I went back to OHCI and can't seem to get any USB HDs working as 
>> is. As soon as the partition table should be read out I run into a timeout and 
>> the HCI driver just sends a reset after n seconds.
>> 
>> The fun thing is that 
>> as soon as I also plug in my USB keyboard, everything works fine in OHCI mode. I 
>> can use the hard drive just fine. This is all on the MINI based 
>> system.
>> 
>> Can you reproduce this on your system 
>> too?
> 
> 
> I haven't tried that exact scenario.
> 
> But I can tell you that the OHCI controllers in the Wii are buggy. The first symptom you see when you use the pristine OHCI support in Linux is that the controller completes the first control transfer but "ignores" all transfers after that one.
> I implemented the mother of all ugliest workarounds (attempting a dummy TD transfer to a control ED after each transfer) and that seemed to keep the controller happy and working, but I've received reports on the irc channel that still there are problems (like disconnection of mass storage devices after hours of operation).
> 
> I haven't yet managed to figure out what's the real cause of the OHCI issues. Something fishy is going on with the OHCI hardware.
> On the other hand EHCI is fine.

So I guess I should just use EHCI then. Would you mind to take a few minutes to get your master branch rebased against the current tip? :-)

KVM works just fine on the Wii btw - I booted a VM perfectly fine. The major issue was swapping being seriously slow though, as the swap was on OHCI.

Alex

Re: [Gc-linux-devel] USB keyboard not working

[Albert H. <alb...@ya...>]

>Btw - I have more odd USB results:
>
>I figured I'd move my 
> root fs from the SD card to a USB drive to speed up things a bit. Hence the try 
> with EHCI. So I went back to OHCI and can't seem to get any USB HDs working as 
> is. As soon as the partition table should be read out I run into a timeout and 
> the HCI driver just sends a reset after n seconds.
>
>The fun thing is that 
> as soon as I also plug in my USB keyboard, everything works fine in OHCI mode. I 
> can use the hard drive just fine. This is all on the MINI based 
> system.
>
>Can you reproduce this on your system 
> too?


I haven't tried that exact scenario.

But I can tell you that the OHCI controllers in the Wii are buggy. The first symptom you see when you use the pristine OHCI support in Linux is that the controller completes the first control transfer but "ignores" all transfers after that one.
I implemented the mother of all ugliest workarounds (attempting a dummy TD transfer to a control ED after each transfer) and that seemed to keep the controller happy and working, but I've received reports on the irc channel that still there are problems (like disconnection of mass storage devices after hours of operation).

I haven't yet managed to figure out what's the real cause of the OHCI issues. Something fishy is going on with the OHCI hardware.
On the other hand EHCI is fine.

Cheers,
Albert



      

Re: [Gc-linux-devel] USB keyboard not working

[Alexander G. <ag...@su...>]

On 19.04.2010, at 21:35, Albert Herranz wrote:

>> So the next thing I 
>> stumbled over is ehci support. As I said earlier I merged your gc-linux changes 
>> into kvm.git which is pretty close to tip. Apparently I'm getting a DSI in the 
>> interrupt handling code now.
>> 
> 
> Obviously your fault :-P

Obviously :). I'd actually guess at interface changes between 2.6.32 and 2.6.34.

> 
>> Basically there are two questions arising 
>> from this:
>> 
>> 1) Is there an easy way to debug such things? I'm having a 
>> hard time reading from a TV screen, the contents scroll out, copy&paste 
>> doesn't work, etc. Netconsole isn't an option I guess because wifi doesn't play 
>> well with it. So what is left to get dumps?
>> 
> 
> The easiest way to debug stuff is to use an "usbgecko".
> It's an adapter that plugs into a memory card slot of the gamecube/wii on one side and a USB port on your PC on the other side. It provides a USB serial connection on the PC and a simple SPI interface on the gamecube/wii which allows to send/receive data to the PC.

Phew - sounds like me "need to buy" list is getting bigger and bigger :).

> 
>> 2) Would you mind rebasing 
>> your master to something more current 
>> :-).
> 
> 
> I decided to mainline code instead of continuing development out of tree.
> See www.gc-linux.org/wiki/Mainline_Kernel for a current status of what's already in.

Yeah, but that feature set is certainly not enough to actually do something with the Wii :-).

> But, as mainlining is taking more time than I expected (for example, I'm stuck waiting for some USB and swiotlb core changes that the EHCI driver patches for mainline depends on) I may eventually integrate as-is the old MIKE series into a mainline-based branch. While doing that, I'll get rid of all IOS-based support which I don't plan to support on the mainline kernel.

Makes sense. I was merely stating that I'd love to have your "master" tree be synced to what's upstream now. There are a lot of conflicts between your tree that actually has all the drivers and tip.


Btw - I have more odd USB results:

I figured I'd move my root fs from the SD card to a USB drive to speed up things a bit. Hence the try with EHCI. So I went back to OHCI and can't seem to get any USB HDs working as is. As soon as the partition table should be read out I run into a timeout and the HCI driver just sends a reset after n seconds.

The fun thing is that as soon as I also plug in my USB keyboard, everything works fine in OHCI mode. I can use the hard drive just fine. This is all on the MINI based system.

Can you reproduce this on your system too?


Alex

Re: [Gc-linux-devel] USB keyboard not working

[Albert H. <alb...@ya...>]

>So the next thing I 
> stumbled over is ehci support. As I said earlier I merged your gc-linux changes 
> into kvm.git which is pretty close to tip. Apparently I'm getting a DSI in the 
> interrupt handling code now.
>

Obviously your fault :-P

>Basically there are two questions arising 
> from this:
>
>1) Is there an easy way to debug such things? I'm having a 
> hard time reading from a TV screen, the contents scroll out, copy&paste 
> doesn't work, etc. Netconsole isn't an option I guess because wifi doesn't play 
> well with it. So what is left to get dumps?
>

The easiest way to debug stuff is to use an "usbgecko".
It's an adapter that plugs into a memory card slot of the gamecube/wii on one side and a USB port on your PC on the other side. It provides a USB serial connection on the PC and a simple SPI interface on the gamecube/wii which allows to send/receive data to the PC.

>2) Would you mind rebasing 
> your master to something more current 
> :-).


I decided to mainline code instead of continuing development out of tree.
See www.gc-linux.org/wiki/Mainline_Kernel for a current status of what's already in.

But, as mainlining is taking more time than I expected (for example, I'm stuck waiting for some USB and swiotlb core changes that the EHCI driver patches for mainline depends on) I may eventually integrate as-is the old MIKE series into a mainline-based branch. While doing that, I'll get rid of all IOS-based support which I don't plan to support on the mainline kernel.

Cheers,
Albert



      

Re: [Gc-linux-devel] USB keyboard not working

[Alexander G. <ag...@su...>]

On 19.04.2010, at 15:29, Albert Herranz wrote:

> Hi,
> 
>> Does that 
>> register have to be flipped from the Arm side or can the PPC side do it? If it's 
>> available on the PPC, why not put the flipping in the early boot code and not 
>> require mini at 
>> all?
> 
> As you guessed, that register needs to be set from the ARM side.

I see. That explains why.

So the next thing I stumbled over is ehci support. As I said earlier I merged your gc-linux changes into kvm.git which is pretty close to tip. Apparently I'm getting a DSI in the interrupt handling code now.

Basically there are two questions arising from this:

1) Is there an easy way to debug such things? I'm having a hard time reading from a TV screen, the contents scroll out, copy&paste doesn't work, etc. Netconsole isn't an option I guess because wifi doesn't play well with it. So what is left to get dumps?

2) Would you mind rebasing your master to something more current :-).


Alex

Re: [Gc-linux-devel] USB keyboard not working

[Albert H. <alb...@ya...>]

Hi,

>Does that 
> register have to be flipped from the Arm side or can the PPC side do it? If it's 
> available on the PPC, why not put the flipping in the early boot code and not 
> require mini at 
> all?

As you guessed, that register needs to be set from the ARM side.

Cheers,
Albert


      

Re: [Gc-linux-devel] USB keyboard not working

[Alexander G. <ag...@su...>]

On 19.04.2010, at 14:49, Albert Herranz wrote:

> Hi,
> 
>> It's 
>> just a generic HID device. Just to be sure I went to the list of all USB HID 
>> devices and activated everything - no luck. I wonder what's going wrong there. 
>> The enumeration does work, the device gets detected and even added as a HID 
>> device to the system. Just pressing keys doesn't help. Weird.
> 
> 
> Yeah, weird.
> Maybe we can find something if you post the dmesg output of the relevant USB-related messages when plugging the keyboard on a gc-linux kernel and the same for a "normal" linux kernel where the device works.

Yikes. Call me stupid. The battery was depleted :).

> 
>> Oh, nice. Maybe I'll just get one of those and 
>> not care about that USB keyboard.
> 
> 
> It may be simpler to switch to another USB keyboard if that _really_ doesn't work.
> All keyboards I have tested so far do work...

Too late - I'll need one for the GC anyways.

> 
>> I'm 
>> pretty sure the Arm-hack doesn't work on my Wii, so I'm out of luck 
>> there.
> 
> 
> AFAIK, you can always run MINI via BootMii as IOS as opposed to BootMii as Boot2.

Hrm, alright. I'll give that a try.

> 
>> Why exactly is that a requirement anyways? IIRC there's a way to 
>> give full access to all device's MMIO regions to the 
>> PPC.
> 
> When I refer to a MINI-based kernel, I'm actually talking about a kernel handling all devices in the PPC side, directly accessing registers via MMIO.
> The MINI IPC mechanism is not used anymore since the AHBPROT register was discovered, but we keep the MINI-kernel name to avoid even more naming confussion/mess. (In any case, the kernel is booted by MINI in the MINI-based kernel).

Does that register have to be flipped from the Arm side or can the PPC side do it? If it's available on the PPC, why not put the flipping in the early boot code and not require mini at all?

Alex

Re: [Gc-linux-devel] USB keyboard not working

[Albert H. <alb...@ya...>]

Hi,

>It's 
> just a generic HID device. Just to be sure I went to the list of all USB HID 
> devices and activated everything - no luck. I wonder what's going wrong there. 
> The enumeration does work, the device gets detected and even added as a HID 
> device to the system. Just pressing keys doesn't help. Weird.


Yeah, weird.
Maybe we can find something if you post the dmesg output of the relevant USB-related messages when plugging the keyboard on a gc-linux kernel and the same for a "normal" linux kernel where the device works.

>Oh, nice. Maybe I'll just get one of those and 
> not care about that USB keyboard.


It may be simpler to switch to another USB keyboard if that _really_ doesn't work.
All keyboards I have tested so far do work...

>I'm 
> pretty sure the Arm-hack doesn't work on my Wii, so I'm out of luck 
> there.


AFAIK, you can always run MINI via BootMii as IOS as opposed to BootMii as Boot2.

>Why exactly is that a requirement anyways? IIRC there's a way to 
> give full access to all device's MMIO regions to the 
> PPC.

When I refer to a MINI-based kernel, I'm actually talking about a kernel handling all devices in the PPC side, directly accessing registers via MMIO.
The MINI IPC mechanism is not used anymore since the AHBPROT register was discovered, but we keep the MINI-kernel name to avoid even more naming confussion/mess. (In any case, the kernel is booted by MINI in the MINI-based kernel).

Cheers,
Albert


      

Re: [Gc-linux-devel] USB keyboard not working

[Alexander G. <ag...@su...>]

On 19.04.2010, at 08:34, Albert Herranz wrote:

>> Howdy,
> 
> Hi,
> 
>> After spending several hours trying to merge the gc-linux master 
>> branch into my KVM branch, I finally got a kernel that boots and runs seemingly 
>> well. Unfortunately, I can not use my USB keyboard.
>> 
>> Is there any know 
>> bugs when using the IOS USB support? I certainly remember that the keyboard did 
>> work with one random older binary blob kernel I got from somewhere on the wii - 
>> and that was 100% running on IOS.
>> 
> 
> Running under IOS has a few limitations regarding USB hubs (hot plug of devices into hubs doesn't work) and configuration descriptor parsing. Also, the USB stack is limited in this case to USB 1.x mode.
> Other than that I'm not aware of any other bugs for the IOS-based kernel USB support.
> 
> I'd make sure that your specific USB keyboard support is enabled on your kernel configuration.
> The default configuration does not enable all possible USB HID devices.

It's just a generic HID device. Just to be sure I went to the list of all USB HID devices and activated everything - no luck. I wonder what's going wrong there. The enumeration does work, the device gets detected and even added as a HID device to the system. Just pressing keys doesn't help. Weird.

> 
>> I've also stumbled over the SI 
>> keyboard. How exactly does that 
>> work?
> 
> 
> That's a driver for a special keyboard (and some adapter clones) designed to play Phantasy Star Online.
> The keyboard (or the keyboard adapter) plugs directly on a gamepad controller port.

Oh, nice. Maybe I'll just get one of those and not care about that USB keyboard.

> 
> Cheers,
> Albert
> 
> PS: Note that IOS-based kernels are now deprecated. "Active" development is currently only done on MINI-based kernels.

I'm pretty sure the Arm-hack doesn't work on my Wii, so I'm out of luck there.

Why exactly is that a requirement anyways? IIRC there's a way to give full access to all device's MMIO regions to the PPC.


Alex

[Gc-linux-devel] Anyone up for some bootmii (mini) hacking?

[Brad N. <big...@gm...>]

I had an idea for a (relatively) simple way to allow booting
linux+mini from USB or other sources - alter mini so that when it
loads, it checks some predefined spot in RAM for ARM and PPC code, and
if present uses that instead of going out to SD.  All the loader would
have to do then is get the files into RAM and switch IOS to bootmii.

Needing to use an SD card kinda sucks, especially when there's some
compatibility issues.

I see the bootmii/mini source is publicly available but I'm not
familiar with what's necessary to update the installed IOS with it.

Re: [Gc-linux-devel] USB keyboard not working

[Albert H. <alb...@ya...>]

> Howdy,

Hi,

>After spending several hours trying to merge the gc-linux master 
> branch into my KVM branch, I finally got a kernel that boots and runs seemingly 
> well. Unfortunately, I can not use my USB keyboard.
>
>Is there any know 
> bugs when using the IOS USB support? I certainly remember that the keyboard did 
> work with one random older binary blob kernel I got from somewhere on the wii - 
> and that was 100% running on IOS.
>

Running under IOS has a few limitations regarding USB hubs (hot plug of devices into hubs doesn't work) and configuration descriptor parsing. Also, the USB stack is limited in this case to USB 1.x mode.
Other than that I'm not aware of any other bugs for the IOS-based kernel USB support.

I'd make sure that your specific USB keyboard support is enabled on your kernel configuration.
The default configuration does not enable all possible USB HID devices.

>I've also stumbled over the SI 
> keyboard. How exactly does that 
> work?


That's a driver for a special keyboard (and some adapter clones) designed to play Phantasy Star Online.
The keyboard (or the keyboard adapter) plugs directly on a gamepad controller port.

Cheers,
Albert

PS: Note that IOS-based kernels are now deprecated. "Active" development is currently only done on MINI-based kernels.



      

[Gc-linux-devel] USB keyboard not working

[Alexander G. <ag...@su...>]

Howdy,

After spending several hours trying to merge the gc-linux master branch into my KVM branch, I finally got a kernel that boots and runs seemingly well. Unfortunately, I can not use my USB keyboard.

Is there any know bugs when using the IOS USB support? I certainly remember that the keyboard did work with one random older binary blob kernel I got from somewhere on the wii - and that was 100% running on IOS.

I've also stumbled over the SI keyboard. How exactly does that work?


Alex

Re: [Gc-linux-devel] Ubuntu: Wii Remix?

[Muzer <muz...@gm...>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

James Lake wrote:
> 'Lo list:
> 
> Though I've never tried to hack together a modified operating system,
> I wanted to know if something is feasible related to Ubuntu Linux.
> 
> For starters, I am well aware of the memory restrictions on the Wii.
> We can skip that part when it comes to me not thinking.
> 
> However, there are many different builds of Ubuntu, and I was
> wondering if a modified Xubuntu running minimum with a lighter window
> manager, such as Blackbox or even the basic X11 we all love, would be
> reasonable? From the Ubuntu docs, it seems that Xubuntu itself used to
> run (terribly) on only 64mb RAM, albeit with terrible response. My
> idea would either invovlve creating a new windowing system for Ubuntu
> on the 10-foot paradigm or using something similar to one of the
> previously mentioned builds.
> 
> Is this feasible? If so, what parts of the base Linux Kernal, exactly,
> have you guys ported to the Wii and what parts of a distribution
> source do I need to change to use/include them?
>

Well, there is already Fluxbuntu (IIRC) which uses fluxbox (not official
though). The currently in-use kernel is 2.6.32, which is before the most
basic Wii support - so you would have to either just use the
bog-standard MIKE kernel, or use the MIKE patches to patch the Ubuntu
kernel (I don't see why not).

You then have the other problem that PPC is no longer handled by
mainline Ubuntu, instead by the community (see for example PSUbuntu for
the PS3) - so you'd probably have a lot of work on your hands.

Hope this helps,

Muzer.

> 
> Thanks for your help,
> 
> ~ J. Lake
> 
> ------------------------------------------------------------------------------
> Download Intel® Parallel Studio Eval
> Try the new software tools for yourself. Speed compiling, find bugs
> proactively, and fine-tune applications for parallel performance.
> See why Intel Parallel Studio got high marks during beta.
> http://p.sf.net/sfu/intel-sw-dev
> _______________________________________________
> gc-linux-devel mailing list
> gc-...@li...
> https://lists.sourceforge.net/lists/listinfo/gc-linux-devel
> 


- --
- -----BEGIN GEEK CODE BLOCK-----
Version: 3.1
GCS/CM/IT d>++ s+:- a--- C+++ UL+++>++++ P+>+++ L+++>+++++ E---->---
W+++ N o? K? w--- O+ M-- V- PS PE? Y-- PGP+++ t+ 5? X- R-- tv+ b++ DI D
G++ e- h! !r y
- ------END GEEK CODE BLOCK------
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJLiAtVAAoJEJzDgfhec8C1uiMIALUH9WXedVWGM58Aoeg35tK2
JCgK89t2WFoFAY72pq0XXemFbOxCMo30EchigwjZhfPgeas7tpEhmPwFwqMNu/U9
iteQp8/AjvmBlveNOYSVn1QOvUHvGkRYwidb9LanoIwOjDYnemt6uYM38mOwz+9t
buASogvAnGFvhAR6lmF/vNA6X2JxKKWCB3YH4QyACGF7C5yOJMuOD2GpZ5AH58QZ
EyK8qno0CSVijd2BuYRvj9vqgSBI4iR9qMAHs4Kngx+9tAGfDteg+/zbkOxGC08u
DcF4Lrzc2LLgAytD3duian0fCeQRc97YcbpZH31JPxiKdE5wYH8ANqmr1mWvFu8=
=lQ+O
-----END PGP SIGNATURE-----