Re: 8.0-RELEASE-i386-memstick fixit - No USB devices found!
On Tue, 8 Dec 2009 00:48:21 +1100 (EST) Ian Smith smi...@nimnet.asn.au wrote: If nothing else, might adding a quick (try Options/Rescan Devices) to the No USB devices message text help some folks out of this quandary? Since it looks like major work to sysinstall isn't going to happen I've committed the change to the error message. -- Bruce Cran ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: 8.0-RELEASE-i386-memstick fixit - No USB devices found!
On Mon, 13 Dec 2010, Bruce Cran wrote:
On Tue, 8 Dec 2009 00:48:21 +1100 (EST)
Ian Smith smi...@nimnet.asn.au wrote:
If nothing else, might adding a quick (try Options/Rescan Devices)
to the No USB devices message text help some folks out of this
quandary?
Since it looks like major work to sysinstall isn't going to happen
I've committed the change to the error message.
Thanks Bruce, may it save a little head-scratching. Oh, just in case;
that was written before I noticed that there were two of these ..
smithi on t23% find . -exec grep -H 'USB devices' {} \;
./install.c:msgConfirm(No USB devices found!);
./media.c: msgConfirm(No USB devices found!);
cheers, Ian
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: 8.0-RELEASE-i386-memstick fixit - No USB devices found!
On Thu, Dec 10, 2009 at 2:20 AM, Ian Smith smi...@nimnet.asn.au wrote: On Sat, 5 Dec 2009, Randi Harper wrote: On Sat, Dec 5, 2009 at 4:01 AM, Ian Smith smi...@nimnet.asn.au wrote: In freebsd-questions Digest, Vol 286, Issue 12, Message 7 On Fri, 27 Nov 2009 06:51:50 -0800 Randi Harper ra...@freebsd.org wrote: On Fri, Nov 27, 2009 at 5:00 AM, Derek (freebsd lists) 48225...@razorfever.net wrote: [..] I made the memstick.img by dd as per the release page on my Thinkpad T23. It only sports USB 1.0 ports, and while I was confident of the dd (which took ~25m at ~600kB/s), I didn't really expect a 2002 laptop to boot from the image, but on seeing the USB stick show up in its BIOS and promoting it in the disk boot order, it did! Never underestimate IBM .. [..] So .. booted into sysinstall, fdisk and label ad0s4, leave boot0 as was, committed that much after two earlier attempts failed due to the below, quit to reboot, checked the labelling, redid the mount points, all ok. Picked pretty much all distributions from custom install, then of course had to select media. Picked USB - and got about what Derek did, no USB disk found. Very long story short: googled for ages and found a forum thread about this very problem, in which someone suggested Options / Rescan Devices then trying again. The OP there said it didn't work for him, but it sure did for me! After knowing that, the install went pretty smoothly, modulo not getting fc-10 to install by FTP, but that's another issue.. And just now, prompted by this thread I tried selecting Fixit, to again get what Derek did. And again, Options / Rescan Devices fixed it for me. Maybe it will for Derek and/or maybe provide another clue? Maybe sysinstall could try a device rescan itself in that circumstance? This is a known issue. It would be possible to write in a hack to fix this problem that would be fairly quick to implement, but sysinstall already has one too many bandaids in place. I'd rather take a little bit of extra time and fix the underlying problem, especially since there is this workaround (forcing a device rescan) that seems to work for users in the meanwhile. At best it's an 'unknown known' :) Except for this present thread, my 'googling for ages' found nothing in FreeBSD lists about it. I was so close to giving up until I could go somewhere to burn a DVD, by then. I appreciate your disinclination to extend that message in sysinstall, it's been about to die for so long it's no longer funny, still it would have saved me half a day, and I'm sure I won't be the last person to run into this. I guess I should file a PR with a patch .. If you want to supply a patch that changes the error message in not finding a valid USB device, go for it. I'll push it through. One of the ideas I've been kicking around is consolidating some of the menu options and having sysinstall look for valid media on all removable devices (USB/CDROM/floppy), with the option to manually set it still available in the Options menu. I'm curious to see what other people think of this first, though. It does dumb down the install, but it still gives advanced users the option of specifying media. If you want to chuckle, take a look at sysinstall's devices.c and how it defines a valid USB device (hint: think DD). :) sysinstall was written back in the good 'ol days of pre-devfs and hasn't been updated much since. When it first runs, it does a device scan - that is, there's this really ugly data structure of all possible devices and a description/limit for each. So, just for example (and I'm not checking the code, so this value is probably wrong), say there's an entry for 'fxp' that is a type network with a limit of 16 devices - it's going to poke the system looking for fxp0, fxp1, ..., fxp15. It's doing this for every single network card, all possible disk devices, everything. Back in the day when computers were slower, this process could take a while, so it only happened once unless the user selected it again. But now, a rescan on my T23 was quite fast, and it's only a P3 1133MHz. I wish we could just disregard all the limitations of older hardware (this would make life so much easier!), but the fact remains that there are people that still install freebsd on ridiculously old computers. The smallest group tends to be the most vocal, or so I've found. Needless to say, this is extremely inefficient (sysinstall code has to be changed any time a new driver is added, too!) and there's a lot of better ways to do this. It's very easy to pull a list of network cards, disks, etc, but the work in moving away from that ugly data structure is no small job. Right now, much of my time is being taken up in trying to get gpt support into sysinstall, but getting rid of that data structure is high in my
Re: 8.0-RELEASE-i386-memstick fixit - No USB devices found!
On Sat, 5 Dec 2009, Randi Harper wrote: On Sat, Dec 5, 2009 at 4:01 AM, Ian Smith smi...@nimnet.asn.au wrote: In freebsd-questions Digest, Vol 286, Issue 12, Message 7 On Fri, 27 Nov 2009 06:51:50 -0800 Randi Harper ra...@freebsd.org wrote: On Fri, Nov 27, 2009 at 5:00 AM, Derek (freebsd lists) 48225...@razorfever.net wrote: [..] I made the memstick.img by dd as per the release page on my Thinkpad T23. It only sports USB 1.0 ports, and while I was confident of the dd (which took ~25m at ~600kB/s), I didn't really expect a 2002 laptop to boot from the image, but on seeing the USB stick show up in its BIOS and promoting it in the disk boot order, it did! Never underestimate IBM .. [..] So .. booted into sysinstall, fdisk and label ad0s4, leave boot0 as was, committed that much after two earlier attempts failed due to the below, quit to reboot, checked the labelling, redid the mount points, all ok. Picked pretty much all distributions from custom install, then of course had to select media. Picked USB - and got about what Derek did, no USB disk found. Very long story short: googled for ages and found a forum thread about this very problem, in which someone suggested Options / Rescan Devices then trying again. The OP there said it didn't work for him, but it sure did for me! After knowing that, the install went pretty smoothly, modulo not getting fc-10 to install by FTP, but that's another issue.. And just now, prompted by this thread I tried selecting Fixit, to again get what Derek did. And again, Options / Rescan Devices fixed it for me. Maybe it will for Derek and/or maybe provide another clue? Maybe sysinstall could try a device rescan itself in that circumstance? This is a known issue. It would be possible to write in a hack to fix this problem that would be fairly quick to implement, but sysinstall already has one too many bandaids in place. I'd rather take a little bit of extra time and fix the underlying problem, especially since there is this workaround (forcing a device rescan) that seems to work for users in the meanwhile. At best it's an 'unknown known' :) Except for this present thread, my 'googling for ages' found nothing in FreeBSD lists about it. I was so close to giving up until I could go somewhere to burn a DVD, by then. I appreciate your disinclination to extend that message in sysinstall, it's been about to die for so long it's no longer funny, still it would have saved me half a day, and I'm sure I won't be the last person to run into this. I guess I should file a PR with a patch .. sysinstall was written back in the good 'ol days of pre-devfs and hasn't been updated much since. When it first runs, it does a device scan - that is, there's this really ugly data structure of all possible devices and a description/limit for each. So, just for example (and I'm not checking the code, so this value is probably wrong), say there's an entry for 'fxp' that is a type network with a limit of 16 devices - it's going to poke the system looking for fxp0, fxp1, ..., fxp15. It's doing this for every single network card, all possible disk devices, everything. Back in the day when computers were slower, this process could take a while, so it only happened once unless the user selected it again. But now, a rescan on my T23 was quite fast, and it's only a P3 1133MHz. Needless to say, this is extremely inefficient (sysinstall code has to be changed any time a new driver is added, too!) and there's a lot of better ways to do this. It's very easy to pull a list of network cards, disks, etc, but the work in moving away from that ugly data structure is no small job. Right now, much of my time is being taken up in trying to get gpt support into sysinstall, but getting rid of that data structure is high in my priority list, especially since there's a workaround. Old/cheap USB flash sticks seem to be the main offender, as they are slow to be recognized/probed, and sysinstall has already finished it's device scan by then. Point taken, but an unknown workaround is no use to the newbie installer (see my prior whinge to Manolis re the X installation menu going away) Yes, I was using an older 1GB Shintaro stick, the only one on hand, on a machine using USB 1.0 only, but I doubt I'll be the only one; sysinstall has always striven to work with other than just top-range newer kit. I do know how hard it is for developers to remember what mortals don't know, or to imagine why folks might not be running more recent gear :) While I'm at it .. selecting 'Holographic Shell', while in that state at least, brings up a shell that (perhaps due to stick not being mounted?) has no ls command, making navigation difficult :) pwd works, set works, but no ls. Later (from debug msgs on vty1) I saw that I'd been perhaps in /stand and only much later
Re: 8.0-RELEASE-i386-memstick fixit - No USB devices found!
Ian Smith wrote: Very long story short: googled for ages and found a forum thread about this very problem, in which someone suggested Options / Rescan Devices then trying again. The OP there said it didn't work for him, but it sure did for me! snip Options / Rescan Devices fixed it for me. Maybe it will for Derek and/or maybe provide another clue? Indeed this works for me. I've added a follow-up to the PR. Thanks for the tip! - Derek ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: 8.0-RELEASE-i386-memstick fixit - No USB devices found!
On Mon, 7 Dec 2009, Derek (freebsd lists) wrote: Ian Smith wrote: Options / Rescan Devices fixed it for me. Maybe it will for Derek and/or maybe provide another clue? Indeed this works for me. I've added a follow-up to the PR. Thanks for the tip! Good to hear. Randi, thanks for your detailed response. Picked up the 'flu visiting Sydney and have been well out of it; hoping for a little energy soon. If nothing else, might adding a quick (try Options/Rescan Devices) to the No USB devices message text help some folks out of this quandary? cheers, Ian ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: 8.0-RELEASE-i386-memstick fixit - No USB devices found!
In freebsd-questions Digest, Vol 286, Issue 12, Message 7 On Fri, 27 Nov 2009 06:51:50 -0800 Randi Harper ra...@freebsd.org wrote: On Fri, Nov 27, 2009 at 5:00 AM, Derek (freebsd lists) 48225...@razorfever.net wrote: Hi, Just wondering if anyone else out there has successfully gotten the 8.0-RELEASE-i386-memstick fixit prompt up. It boots fine, and sysinstall comes up, but I continually get No USB devices found! when I go to the fixit/USB option. When I switch to the debug tty, I see da0, and all my device parameters. I've even created a second USB stick, and stuck it in and tried. No joy. Anyways, has anyone successfully gotten the 8.0-RELEASE-i386-memstick fixit prompt up? Thanks! - Derek That's really weird. I can't say that I've seen this problem. It sounds like you're trying to load the livefs - can you bring up a normal fixit shell prompt and see what entries you have in /dev for da0*? There should be a da0a. Due to sysinstall weirdness, adding this USB support was somewhat of a hack, as it doesn't look for da0 - it looks for da0a. :P Hi Randi, I had the same problem, rather more substantially, installing 8.0 from the memstick.img. This thread and to you seems to be where I should report what I remember of the process, only later finding all this. I made the memstick.img by dd as per the release page on my Thinkpad T23. It only sports USB 1.0 ports, and while I was confident of the dd (which took ~25m at ~600kB/s), I didn't really expect a 2002 laptop to boot from the image, but on seeing the USB stick show up in its BIOS and promoting it in the disk boot order, it did! Never underestimate IBM .. I was being very careful, as I wanted to install 8.0 on ad0s4, hopefully not damaging my 7.0-R on ad0s2, still having memories of a 3.3-R install in similar circumstances that went horribly wrong, 8? years ago :) So .. booted into sysinstall, fdisk and label ad0s4, leave boot0 as was, committed that much after two earlier attempts failed due to the below, quit to reboot, checked the labelling, redid the mount points, all ok. Picked pretty much all distributions from custom install, then of course had to select media. Picked USB - and got about what Derek did, no USB disk found. Very long story short: googled for ages and found a forum thread about this very problem, in which someone suggested Options / Rescan Devices then trying again. The OP there said it didn't work for him, but it sure did for me! After knowing that, the install went pretty smoothly, modulo not getting fc-10 to install by FTP, but that's another issue.. And just now, prompted by this thread I tried selecting Fixit, to again get what Derek did. And again, Options / Rescan Devices fixed it for me. Maybe it will for Derek and/or maybe provide another clue? Maybe sysinstall could try a device rescan itself in that circumstance? While I'm at it .. selecting 'Holographic Shell', while in that state at least, brings up a shell that (perhaps due to stick not being mounted?) has no ls command, making navigation difficult :) pwd works, set works, but no ls. Later (from debug msgs on vty1) I saw that I'd been perhaps in /stand and only much later found that find worked and served as ls .. One more thing, while I remember .. seeing the USB stick is here ad0a, isn't that the old 'dangerously dedicated mode' now dropped from 8.0? And to be a real pest with questions, where in CVS do I find the script or whatever makes memstick.img in the first place? cheers, Ian ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: 8.0-RELEASE-i386-memstick fixit - No USB devices found!
On Sat, 5 Dec 2009, Ian Smith wrote: One more thing, while I remember .. seeing the USB stick is here ad0a, isn't that the old 'dangerously dedicated mode' now dropped from 8.0? That's da0a of course. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: 8.0-RELEASE-i386-memstick fixit - No USB devices found!
On Sat, Dec 5, 2009 at 4:01 AM, Ian Smith smi...@nimnet.asn.au wrote: In freebsd-questions Digest, Vol 286, Issue 12, Message 7 On Fri, 27 Nov 2009 06:51:50 -0800 Randi Harper ra...@freebsd.org wrote: On Fri, Nov 27, 2009 at 5:00 AM, Derek (freebsd lists) 48225...@razorfever.net wrote: Hi, Just wondering if anyone else out there has successfully gotten the 8.0-RELEASE-i386-memstick fixit prompt up. It boots fine, and sysinstall comes up, but I continually get No USB devices found! when I go to the fixit/USB option. When I switch to the debug tty, I see da0, and all my device parameters. I've even created a second USB stick, and stuck it in and tried. No joy. Anyways, has anyone successfully gotten the 8.0-RELEASE-i386-memstick fixit prompt up? Thanks! - Derek That's really weird. I can't say that I've seen this problem. It sounds like you're trying to load the livefs - can you bring up a normal fixit shell prompt and see what entries you have in /dev for da0*? There should be a da0a. Due to sysinstall weirdness, adding this USB support was somewhat of a hack, as it doesn't look for da0 - it looks for da0a. :P Hi Randi, I had the same problem, rather more substantially, installing 8.0 from the memstick.img. This thread and to you seems to be where I should report what I remember of the process, only later finding all this. I made the memstick.img by dd as per the release page on my Thinkpad T23. It only sports USB 1.0 ports, and while I was confident of the dd (which took ~25m at ~600kB/s), I didn't really expect a 2002 laptop to boot from the image, but on seeing the USB stick show up in its BIOS and promoting it in the disk boot order, it did! Never underestimate IBM .. I was being very careful, as I wanted to install 8.0 on ad0s4, hopefully not damaging my 7.0-R on ad0s2, still having memories of a 3.3-R install in similar circumstances that went horribly wrong, 8? years ago :) So .. booted into sysinstall, fdisk and label ad0s4, leave boot0 as was, committed that much after two earlier attempts failed due to the below, quit to reboot, checked the labelling, redid the mount points, all ok. Picked pretty much all distributions from custom install, then of course had to select media. Picked USB - and got about what Derek did, no USB disk found. Very long story short: googled for ages and found a forum thread about this very problem, in which someone suggested Options / Rescan Devices then trying again. The OP there said it didn't work for him, but it sure did for me! After knowing that, the install went pretty smoothly, modulo not getting fc-10 to install by FTP, but that's another issue.. And just now, prompted by this thread I tried selecting Fixit, to again get what Derek did. And again, Options / Rescan Devices fixed it for me. Maybe it will for Derek and/or maybe provide another clue? Maybe sysinstall could try a device rescan itself in that circumstance? This is a known issue. It would be possible to write in a hack to fix this problem that would be fairly quick to implement, but sysinstall already has one too many bandaids in place. I'd rather take a little bit of extra time and fix the underlying problem, especially since there is this workaround (forcing a device rescan) that seems to work for users in the meanwhile. sysinstall was written back in the good 'ol days of pre-devfs and hasn't been updated much since. When it first runs, it does a device scan - that is, there's this really ugly data structure of all possible devices and a description/limit for each. So, just for example (and I'm not checking the code, so this value is probably wrong), say there's an entry for 'fxp' that is a type network with a limit of 16 devices - it's going to poke the system looking for fxp0, fxp1, ..., fxp15. It's doing this for every single network card, all possible disk devices, everything. Back in the day when computers were slower, this process could take a while, so it only happened once unless the user selected it again. Needless to say, this is extremely inefficient (sysinstall code has to be changed any time a new driver is added, too!) and there's a lot of better ways to do this. It's very easy to pull a list of network cards, disks, etc, but the work in moving away from that ugly data structure is no small job. Right now, much of my time is being taken up in trying to get gpt support into sysinstall, but getting rid of that data structure is high in my priority list, especially since there's a workaround. Old/cheap USB flash sticks seem to be the main offender, as they are slow to be recognized/probed, and sysinstall has already finished it's device scan by then. While I'm at it .. selecting 'Holographic Shell', while in that state at least, brings up a shell that (perhaps due to stick not being mounted?) has no ls command, making navigation
Re: 8.0-RELEASE-i386-memstick fixit - No USB devices found!
For the archives, there's now a PR for this: bin/140972 - Derek ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
8.0-RELEASE-i386-memstick fixit - No USB devices found!
Hi, Just wondering if anyone else out there has successfully gotten the 8.0-RELEASE-i386-memstick fixit prompt up. It boots fine, and sysinstall comes up, but I continually get No USB devices found! when I go to the fixit/USB option. When I switch to the debug tty, I see da0, and all my device parameters. I've even created a second USB stick, and stuck it in and tried. No joy. Anyways, has anyone successfully gotten the 8.0-RELEASE-i386-memstick fixit prompt up? Thanks! - Derek ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: 8.0-RELEASE-i386-memstick fixit - No USB devices found!
On Fri, Nov 27, 2009 at 5:00 AM, Derek (freebsd lists) 48225...@razorfever.net wrote: Hi, Just wondering if anyone else out there has successfully gotten the 8.0-RELEASE-i386-memstick fixit prompt up. It boots fine, and sysinstall comes up, but I continually get No USB devices found! when I go to the fixit/USB option. When I switch to the debug tty, I see da0, and all my device parameters. I've even created a second USB stick, and stuck it in and tried. No joy. Anyways, has anyone successfully gotten the 8.0-RELEASE-i386-memstick fixit prompt up? Thanks! - Derek That's really weird. I can't say that I've seen this problem. It sounds like you're trying to load the livefs - can you bring up a normal fixit shell prompt and see what entries you have in /dev for da0*? There should be a da0a. Due to sysinstall weirdness, adding this USB support was somewhat of a hack, as it doesn't look for da0 - it looks for da0a. :P -- randi ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: 8.0-RELEASE-i386-memstick fixit - No USB devices found!
Randi Harper wrote: On Fri, Nov 27, 2009 at 5:00 AM, Derek (freebsd lists) 48225...@razorfever.net wrote: It boots fine, and sysinstall comes up, but I continually get No USB devices found! when I go to the fixit/USB option. Anyways, has anyone successfully gotten the 8.0-RELEASE-i386-memstick fixit prompt up? can you bring up a normal fixit shell prompt and see what entries you have in /dev for da0*? There should be a da0a. Due to sysinstall weirdness, adding this USB support was somewhat of a hack, as it doesn't look for da0 - it looks for da0a. :P When I do Fixit/Shell and switch to tty3 I do: find /dev/ -name da0* and get: ./da0 ./da0a Is this what you mean by normal fixit shell? - Derek ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
