I am currently playing with the 126.96.36.199 kernel, and I suddenly noticed that the 'ohci-hcd' module has two dependencies: 'usbcore' and 'ssb'. Er, 'ssb' is not in the initial ramdisk.
I checked 4.1 and 4.1.1, the same situation with the 188.8.131.52 kernel.
What this means is that USB storage that requires the 'ohci-hcd' module will not be detected in the initial ramdisk, which means that you can't boot from USB nor have a 'pup_save' in USB.
Note that the 'ohci-hcd' driver will get loaded later on (after the switch_root) so you can access the USB drives then. Just not at bootup.
The 'uhci-hcd' driver is the most common USB host driver, and that only requires the 'usbcore' driver, so all is well there.
Amazing that such a serious bug managed to get through all those alpha and beta stages of testing!
Hmmm, does this mean I have to bring out a 4.1.2 second bugfix release? Note, if you have 4.1 or 4.1.1 Unleashed, it is easy to fix this bug -- just edit 'createpuppy' script and add "ssb.ko " to the 'NEEDEDINITRDMODS' variable.
Comments:Posted on 10 Nov 2008, 19:41 by Sage
"does this mean I have to bring out a 4.1.2 second bugfix release?"
Definitely. But might be worth waiting a week or so for any other mission-critical features to turn up.
PS. My P/W didn't auto-insert this morning???
Posted on 10 Nov 2008, 20:42 by lobster
bug will be fixed in alpha 4.2
"does this mean I have to bring out a 4.1.2 second bugfix release?"
I should think that Warren (WhoDo) can add this fix to the Alpha of 4.2 as it is easy to fix from unleashed.
Thanks for 4.1.1 Unleashed which arrived safely in the post today
Posted on 10 Nov 2008, 21:41 by WN2A
If you do generate a 4.1.2 bugfix, maybe wait a week (or so) as per Sage. Especially if that means devx_412.sfs is needed too. I would likely use 4.1.2 on my PC's and Laptops, even with 4.0/4.1 running great.
Posted on 10 Nov 2008, 22:16 by puppymike
Funny I have been using 4.1.1 (upgraded from 4.1) on a SD Card and USB stick with 184.108.40.206 kernel since you released it with no problems booting or with the Puppy save file.
Posted on 10 Nov 2008, 23:42 by eprv
set date and time
Had no problems with USB in 4.11 few kinds of sticks work well,in general this is a remarkably stable and useful edition of Puppy.
but if a bugfix release is considered than when setting time, the screen goes blank for about a minute and only when it comes back it says that it will go blank, could be uncomfortable for new users.
Posted on 10 Nov 2008, 24:37 by dogone
If 4.1.2 must happen, I suggest it address more outstanding 4.1.1 "issues".
Rather than you authoring all these fixes Barry, I suggest we ask the core developers to create a *very* short list of candidate issues for 4.1.2 and help in addressing them. This would minimize the impact on you and might prove an excellent transition exercise.
Posted on 11 Nov 2008, 2:46 by prehistoric
second the motions
This eliminates one big mystery. I also believe we should incorporate other fixes. The suggestion by dogone sounds great.
Posted on 11 Nov 2008, 8:39 by disciple
It looks like the guy who found our forum because he had the same bug as us with Seamonkey/FF/Th crashing when using the insert key in a text entry field has found a workaround. If it works for us too, this would be good for another bug-fix release:
If anyone could locate and fix whatever is breaking pmount it would be good too:
Posted on 11 Nov 2008, 11:05 by Viking Sailor
long term support
Form my reading of the forum it sounds like changing to the 220.127.116.11 kernel is very doable. Considering that the kernel.org's commitment to "long term support" for this kernel. This would give us a base for a new long term support puppy.
Posted on 11 Nov 2008, 15:00 by WhoDo
Bug fix release
"I should think that Warren (WhoDo) can add this fix to the Alpha of 4.2 as it is easy to fix from unleashed.
Thanks for 4.1.1 Unleashed which arrived safely in the post today"
The bug mentioned, and the Pmount problem, are both show stoppers IMHO. That requires an urgent bug fix update, and can't wait for 4.2 - we wouldn't be publicly promoting 4.2alpha as a bug fixed 4.1.1 anyway; that's not what an alpha is for.
I'm with the guys who suggested the devs help Barry roll out a 4.1.2 bug fix release OR provide a patch (if that's possible). That will get to the core users when an alpha wouldn't.
Barry, my CD arrived yesterday too. Thank you, mate. It will save me heaps of time on setting up for 4.2 development.
Posted on 11 Nov 2008, 15:56 by lobster
"I'm with the guys who suggested the devs help Barry roll out a 4.1.2 bug fix release OR provide a patch (if that's possible)."
Sounds good to me. Keep us posted Warren, on 4.2, especially if you need any help.
Also I wonder if this might be a good time (or is it to early) to uses Jeremy's (Pizzasgood) Unleashed SVN system?
Posted on 11 Nov 2008, 23:18 by `f00
edit Release notes
.. with an interim footnote or links on this particular kernel to reflect awareness as many do read them. Good to know for the new friends of Puppy who are looking at options beyond the CDvD :)
Posted on 11 Nov 2008, 23:41 by Pizzasgood
It seems to be working so far, but right now it's just running off my old computer under my bed. Might be better to wait until Caneri gets his servers up and running, which I believe he's now on the verge of (they seem to be online now).
But if y'all want to start using it now anyways, not a big deal. Just let me know in advance so I can bring it up to date and give people proper logins, and disable the testperson account (or maybe just limit that to a specific "sandbox" area).
Posted on 12 Nov 2008, 8:14 by alienjeff
More like ...
"Amazing that such a serious bug managed to get through all those alpha and beta stages of testing!"
Nay. More like par for the course.
Posted on 12 Nov 2008, 16:01 by downsouth
4.1.2 would be nice
Only if you feel like it Barry.
BTW mount.cifs is not in 411 retro.
Posted on 15 Nov 2008, 4:47 by erikson
Booting "full" off usb
I have investigated booting *full* installs off usb devices (flash and hdd) and I have documented my solution in forum thread How to do a full install on external USB hdd
I just added an "additional note" post (post # 21 of that thread) discussing how to patch my special version for this 18.104.22.168 ohci-hcd bug.
If there's sufficient user interest, there might be a way to incorporate full-install booting off usb devices into regular future Puppy releases. It would be a matter of merging my special full-boot initrd with the regular one.
Posted on 20 Nov 2008, 14:02 by disciple
Another candidate bug for a bugfix release
/tmp/versioncleanup/ doesn't show up after an upgrade, pfix=clean, or pfix=ram.
There may well be a simple fix, in which case it would be good for a bugfix release.
Could it be something to do with the change back to having /tmp in ram, and the timing of the creation of the tmpfs?