|
NetBSD Package System (pkgsrc) Installation and upgrading of packages on NetBSD. |
|
Thread Tools | Display Modes |
|
|||
I see that e few mailing lists have a reference to acpitz for sony's and other laptops.
The shutdown-overheating problem is also mentioned in the lists. There is also the sony and spic drivers. Do I need them? http://mail-index.netbsd.org/netbsd-...msg003624.html I edited this to show the mailing list. I'm not sure what the result will be. Will the apm, power and acpi work together or will I need to do a bit of editing? Last edited by Mr-Biscuit; 9th June 2009 at 08:19 AM. |
|
|||
I'll get back to those.
I need to adjust the powerd scripts to keep the cpu cool; but, I don't know what values to add as safe max and min. Estd is installed now. The average temp with gui is 70-75c without 55-60c. I need the gui temp to run at the lower values listed above. I cut the desktop down to xfce4 and WindowMaker- apologies if i am repeating myself. KDM is enabled but, I can disable that and maybe minimalize the desktop more if it would help with temperature control. |
|
||||
pkgsrc pkg_add problems not connecting
Hi Mr-Biscuit
two things: first, to check on the bios of your pc if the board is composed of network and has some extra settings that may be suspended when the connection is very slow, which is the case of ftp://ftp.netbsd.org/pub/pkgsrc/pack...D/i386/5.0/All a little google on the topic of how the board works and how to configure your network If they can not solve, in general, if the problem is that, you have to reboot and then try to install the pkg, example: [su - root -c 'pkg_add -v gnome'] Or you want to install pkg SECOND: if it does not work, income from that PC's browser or to other ftp://ftp.netbsd.org/pub/pkgsrc/pack...D/i386/5.0/All pkg download and you are asking, for example: [gnome*.tbz] and make a copy of that file to the directory ['/var/tmp'] and then try again [su - root -c 'pkg_add -v gnome'] if pkg is calling for the installation, verify the above, the installation continues and if the same thing happen again ... need to repeat the procedure sorry for the way of writing ... I'm not very good with English language and this is directly translated to a program. I hope to provide some response, but that I have solved several of pkg topo. ---------------------------------- ESTO NO ES UN JUEGO!!!! Last edited by topo; 12th June 2009 at 04:41 AM. |
|
|||
I'm compiling the kernel with these results.
g-weebens# config MYKERNEL MYKERNEL:851: `wd0 at atabus0' is orphaned (no `atabus0' found) MYKERNEL:862: `cd0 at atapibus1' is orphaned (no `atapibus1' found) MYKERNEL:863: `sd0 at atapibus0' is orphaned (no `atapibus0' found) *** Stop. g-weebens# dmesg | grep atabus0 atabus0 at piixide0 channel 0 g-weebens# dmesg | grep atapibus0 atapibus0 at umass0: 2 targets sd0 at atapibus0 drive 0: <Sony, MSC-U03, 1.00> disk removable g-weebens# g-weebens# dmesg | grep atapibus1 atapibus1 at atabus1: 2 targets cd0 at atapibus1 drive 0: <SONY CD-RW/DVD-ROM CRX810E, , 1.5a> cdrom removable g-weebens# How do I get it to recognize the hardware? I've already edited MYKERNEL to include the values from dmesg. |
|
||||
Is MYKERNEL just a GENERIC with a few additions, or you stripped it down? Maybe you left out some things:
Code:
$ grep 'ata[bus|pibus]' /usr/src/sys/arch/i386/conf/GENERIC atabus* at ata? wd* at atabus? drive ? flags 0x0000 atapibus* at atapi? cd* at atapibus? drive ? flags 0x0000 # ATAPI CD-ROM drives sd* at atapibus? drive ? flags 0x0000 # ATAPI disk drives st* at atapibus? drive ? flags 0x0000 # ATAPI tape drives uk* at atapibus? drive ? flags 0x0000 # ATAPI unknown
__________________
The best way to learn UNIX is to play with it, and the harder you play, the more you learn. If you play hard enough, you'll break something for sure, and having to fix a badly broken system is arguably the fastest way of all to learn. -Michael Lucas, AbsoluteBSD |
|
|||
g-weebens$ pwd
/usr/src/usr/src/sys/arch/i386/conf g-weebens$ grep 'ata[bus|pibus]' GENERIC #(# atabus* at ata? wd0 at atabus0 drive 0 flags 0x0000 #(# atapibus* at atapi? cd0 at atapibus1 drive 0 flags 0x0000 # ATAPI CD-ROM drives sd0 at atapibus0 drive 0 flags 0x0000 # ATAPI disk drives #(# st* at atapibus? drive ? flags 0x0000 # ATAPI tape drives #(# uk* at atapibus? drive ? flags 0x0000 # ATAPI unknown # NOTE: NoMatch: atabus0 at piixide0 channel 0 # NOTE: NoMatch: atabus1 at piixide0 channel 1 # NOTE: NoMatch: atapibus0 at umass0: 2 targets # NOTE: NoMatch: atapibus1 at atabus1: 2 targets # NOTE: NoMatch: atabus0 at piixide0 channel 0 # NOTE: NoMatch: atabus1 at piixide0 channel 1 # NOTE: NoMatch: atapibus0 at umass0: 2 targets # NOTE: NoMatch: atapibus1 at atabus1: 2 targets g-weebens$ grep 'ata[bus|pibus]' MYKERNEL #(# atabus* at ata? wd0 at atabus0 drive 0 flags 0x0000 #(# atapibus* at atapi? cd0 at atapibus1 drive 0 flags 0x0000 # ATAPI CD-ROM drives sd0 at atapibus0 drive 0 flags 0x0000 # ATAPI disk drives #(# st* at atapibus? drive ? flags 0x0000 # ATAPI tape drives #(# uk* at atapibus? drive ? flags 0x0000 # ATAPI unknown # NOTE: NoMatch: atabus0 at piixide0 channel 0 # NOTE: NoMatch: atabus1 at piixide0 channel 1 # NOTE: NoMatch: atapibus0 at umass0: 2 targets # NOTE: NoMatch: atapibus1 at atabus1: 2 targets # NOTE: NoMatch: atabus0 at piixide0 channel 0 # NOTE: NoMatch: atabus1 at piixide0 channel 1 # NOTE: NoMatch: atapibus0 at umass0: 2 targets # NOTE: NoMatch: atapibus1 at atabus1: 2 targets # NOTE: NoMatch: atabus0 at piixide0 channel 0 # NOTE: NoMatch: atabus1 at piixide0 channel 1 # NOTE: NoMatch: atapibus0 at umass0: 2 targets # NOTE: NoMatch: atapibus1 at atabus1: 2 targets g-weebens$ |
|
|||
I'm going to restart with a new /usr/src directory. It seems that adjustkernel has a bug in it and I do not know which lines need to be uncommented.
This would be the only way I can get estd working. |
|
||||
It seems that you put in GENERIC what you found in dmesg? That's not the way to go. And it seems you did comment some of the lines in GENERIC too. Please use tags when posting command outputs, it is more readable that way.
Best is to update your source so you get fresh code, without errors. Then start compiling your kernel again.
__________________
The best way to learn UNIX is to play with it, and the harder you play, the more you learn. If you play hard enough, you'll break something for sure, and having to fix a badly broken system is arguably the fastest way of all to learn. -Michael Lucas, AbsoluteBSD |
|
|||
I did make depends before I went to work and am running make now. I only uncommented two items from the make file. One was ondemand and the other I forgot.
|
|
|||
It's up and running.
Not able to implement estd or ondemand. Last edited by Mr-Biscuit; 14th June 2009 at 11:34 AM. |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
pkg_add problems with connecting | Mr-Biscuit | NetBSD Package System (pkgsrc) | 2 | 26th May 2009 11:44 AM |
Connecting to router wirelessly | guitarscn | OpenBSD General | 16 | 21st January 2009 03:47 AM |
pkgsrc on OpenBSD | Oko | OpenBSD Packages and Ports | 3 | 22nd December 2008 06:51 PM |
NetBSD 4.0 upgrade and pkgsrc | fenrisW0lf | NetBSD Installation and Upgrading | 3 | 19th June 2008 09:39 PM |
pkgsrc build time excessive! | JMJ_coder | NetBSD Package System (pkgsrc) | 3 | 18th June 2008 08:41 PM |