I'm having some problems
with a new USB drive I just bought, Opensolaris
snv_134 is detecting it at all,
Are there any error messages logged to the console /
the /var/adm/messages file when you hotplug the
USB drive?
tail -f /var/adm/messages
and hot plug the USB drive.
--
This message
j...@opensolaris:~$ ifconfig nge0
ifconfig: status: SIOCGLIFFLAGS: nge0: no such interface
nVidia MCP61 should work in build 73 or newer:
http://bugs.opensolaris.org/bugdatabase/view_bug.do?bug_id=6497473
Is the nge driver matter here? The original message said:
...
And finally,
j...@opensolaris:~$ ifconfig nge0
ifconfig: status: SIOCGLIFFLAGS: nge0: no such interface
nVidia MCP61 should work in build 73 or newer:
http://bugs.opensolaris.org/bugdatabase/view_bug.do?bug_id=6497473
Is there a new network interface after
ifconfig -a plumb
?
In case the
I retested with gcc 3.4.3 and everything works fine.
Using the 4.3.3 compiler, the breakpoint is being set right at the address of
main
before the prologue code is executed. I will need to investigate why
that is happening.
Hmm...
On opensolaris b134, after pkg install gcc-43, and
I can reproduce the problem on my system running bash so I don't think
it is related the the shell:
(gdb) b main
Breakpoint 1 at 0x8050ccc: file g.c, line 4.
(gdb) r
Starting program: /home/gvasick/a.out
Breakpoint 1, main (argc=260904, argv=0xfef90018) at g.c:4
Which compiler,
here's the lshal with all the entires
pertaining to this usbstick
there is 'volume' entry
Hal's volume entry for the usb device
looks good.
I think the next step is that
hal-storage-mount gets started (?),
and it is supposed to mount the
pcfs file system.
Are there any error messages in
hald
fstype gives unknown fs_type
Hmm, fstyp should work, too.
Did you use the block device, /dev/dsk/... ?
also, here's the lshal with all the entires
pertaining to this usbstick
there is 'volume' entry
volume.label = 'USB4G' (string)
...
volume.fstype = 'pcfs' (string)
Hal seems to
b134
usb sticks and usb drives won't automount or by cl
can find devices with format -e or rmformat -l, so
they're there ... just can't mount
What kind of file system is used on these usb devices?
FAT? Or NTFS?
What is reported by pfexec fdisk -R -W - /dev/rdsk/c?t0d0p0 ?
(where
block.device = '/dev/dsk/c6t0d0p0' (string)
...
info.product = 'USB 2.0 FD' (string)
Hmm, is that an USB floppy drive?
I guess there is a floppy media inserted in the drive.
Is the media ok?
Floppy media usually has no MBR partition table, so
pfexec fdisk -R -W - /dev/rdsk/c6t0d0p0
will
pfexec fdisk -R -W - /dev/rdsk/c6t0d0p0
...
* IdAct Bhead Bsect BcylEhead Esect EcylRsect Numsect
1101 1 0 25463 488 63 7855722
,,,
Ok, and pfexec fstyp -v /dev/dsk/c6t0d0p1 ?
Seems to be a pcfs filesystem.
What
yes. this drive is fat32. since the thread started, i
reformated and made sure it had a volume label (which
it didn't before). it still does not automount, but
command line mount now works. STILL ... i'd like to
figure out why drives aren't automounting.
Ok, so usb device drivers, sd disk
yes. this drive is fat32. since the thread started, i
reformated and made sure it had a volume label (which
it didn't before).
Did you already try the fstyp -v /dev/dsk/c6t0d0p1 command?
See also this thread:
http://opensolaris.org/jive/thread.jspa?messageID=344425#344425
(An invalid
Where exactly can I get SNV build 134 from.
http://www.genunix.org/
http://www.genunix.org/distributions/indiana/osol-dev-134-x86.iso
--
This message posted from opensolaris.org
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org
mkfs -F pcfs -o fat=32 /dev/rdsk/c10t0d0p1
*Bad Sig on master boot record!
Did you use fdisk on the /dev/rdsk/c10t0d0p0
device and did you create a Windows LBA
primary fdisk partition?
mkfs -F pcfs -o fat=32 /dev/rdsk/c10t0d0p1:c
*No such logical drive (missing extended partition
I have a 1Tbyte usb external HD that I want to be
able to read with windows and b134. I have tried all
of the below but am unable to get solaris to read and
write to it.
mkfs -F pcfs -o fat=32 /dev/rdsk/c10t0d0p1
*Bad Sig on master boot record!
The following commands would emulate
I attempted to change my display settings and somehow
broke X. It only displays that x can not be started
hit enter for a console prompt. The console prompt
never appears. If I can not get to to the prompt how
can I fix it? Can anyone provide suggestion on how
to boot without X
The ON source was available for us to download at -
OpenSolaris Download Center
http://dlc.sun.com/osol/on/downloads/current/
But it is missing for some time. Anybody knows why?
Found on the above page:
Source tarballs have been deprecated in favour of the onnv
project's Mercurial
I have installed b134 on a clevo laptop. The live cd
booted just fine and the install went on without a
problem. After the install when I reboot the system
comes up with the initial grub screen just after the
OS is selected the screen goes black and the system
reboots.
Did you try tz boot
When I compared the two files with md5sum on each
side, I got different checksums.
I did so a split of the file to 5 GB parts and compared:
Solaris:
...
199d15f5204c14a97d29f86b14cd154b cpartad
Linux:
...
0509b68893216f894ee394c0ab212cd2 cpartad
You could transfer the cpartad 5 GB
I redownloaded the file cpartad and compared it with
cmp -l with the old file:
$ cmp -l cpartad cpartad.old
4962108197 271 371
$ bc
ibase=10
obase=2
271
1
371
101110011
It seems that 5 bits are wrong of the 23GB file transfer.
The differences reported by cmp -l are in
The differences reported by cmp -l are in octal;
so this is actually a single bit error.
But then TCP checksums should discover the problem
That bit could have fllipped both on the sending
or the receiving machine (before or after TCP is
used).
--
This message posted from opensolaris.org
That is, the build mail at least reported
completed, the packages built, and I was able to
update and boot my server from the results.
But, there are still all sorts of errors in the mail
to root. The rest of the garbage in there is all
normal?
The build noise differences is ok. It
Can someone point me to the procedure for how to
install on a memory stick.
Should be identical to the procedure when you install
to a regular hdd.
It gets problematic when you try to connect the installed
usb storage device to a random machine - most likely the
kernel refuses to boot on the
I then did a nightly ./opensolaris.sh from within my
environment. My build system is a dual 2.1GHz
Celeron (64-bit) with 4GB RAM. Should be plenty.
After about 5 hours, the job completed, and I
received the attached mail. I did build as root,
which may be bad, but...
Nothing in there
The laptop still does not power down, because every
30 seconds there is a batch of writes to the hdd drive,
apparently from zfs, and that keeps the hdd powered up.
It was caused by b134 gnome-terminal. I had an iostat
running in a gnome-terminal window, and the periodic
iostat output is
keithk keithc...@gmail.com wrote:
Hi eam1,
I did. After which, I reboot the system. Still nothing happens.
This is a well known bug that was introduced with SXCE build 130.
Is there a bug filed to track this problem?
--
This message posted from opensolaris.org
Putting the flag does not seem to do anything to the
system. Here is my power.conf file:
...
autopmenable
autoS3enable
S3-supportenable
Problem seems to be that all power managed devices
must be at their lowest power level, otherwise
Why does zfs produce a batch of writes every 30 seconds on opensolaris b134
(5 seconds on a post b142 kernel), when the system is idle?
On an idle OpenSolaris 2009.06 (b111) system, /usr/demo/dtrace/iosnoop.d
shows no i/o activity for at least 15 minutes.
The same dtrace test on an idle b134
I am running Opensolaris snv_134 on a dell computer.
I am able to suspend the desktop at will, but does
not seem to be able to set a timeout for the desktop
to suspend after a configurable idle time using Power
Manager. The Power Manager does not offer me the
slider where I can see the idle
ls /dev/dsk/c4t?d0
/dev/dsk/c4t0d0 /dev/dsk/c4t1d0 /dev/dsk/c4t2d0
/dev/dsk/c4t3d0 /dev/dsk/c4t4d0
Are you sure those /dev/dsk/c*d0 entries
are device nodes?
Try ls -l /dev/dsk/c*d0
and ls -lL /dev/dsk/c*d0,
maybe they are files that have been
created by accident by a user user
with root
not found: ddi_get_parent_data
not found: kdi_dvec_memavail
...
krtld: error during initial load/link phase
krtld could neither locate nor resolve symbols for:
/platform/i86pc/kernel/amd64/unix the boot archive.
Most likely the boot archive file
/platform/i86pc/amd64/boot_archive
and/or
Basically, is there a Windows emulator... that will allow me to
run Windows-based applications or Windows itself on
top of OpenSolaris?
http://www.virtualbox.org/
--
This message posted from opensolaris.org
___
opensolaris-discuss mailing list
I don't type pathnames longer than 100 characters,
which is 20 characters wider than a normal page.
Try again with a path name 100 chars and check what
happens. I did verify a failure with Indiana build 134
But I don't use that on my system anyway...:-/
My opensolaris b134 system has
Thank you, I will look into that problem if can help me.
The vbox ticket #6181 probably won't help much.
It is set to closed / fixed, but as far as I understand it,
some superfluous logging was removed from the Solaris
vbox guest kernel module, but the root cause for the
broken auto-resizing
The vbox ticket #6181 have no help.
And the problem isn't fixed.
Hmm, seems I found something...
In the guest window's Machine - Auto-resize Guest Display
menu item (Host-G keyboard shortcut): is the menu item
enabled, and does it show a checked icon?
I just repeated the installation of
Thank you, but I cannot adjust it as I want.
For example, I press Ctrl+F, fullscreen the
VirtualBox, but the OS screen donot change, just fill
black around with it!
Hmm, I wonder if mouse pointer integration
is working with your opensolaris vbox guest?
Some time ago I had a problem with the
I'm getting the following errors when booting from flash:
WARNING:
/p...@0,0/pci1043,8...@1d,7/stor...@2/d...@0,0 (sd1):
Check Condition on REQUEST SENSE
Hmm, the flash device seems to have signaled an
error condition for some (scsi) command; and when
asked for the exact cause for the error
2.) Is there a negative effect if the SATA disks connected to those ports only
run as IDE (aka cmdk driver?)
ata / cmdk has not 64bit dma support, so that the driver
has to use dma bounce buffers to access physical memory
4GB. Using ahci should avoid this issue.
No hotplug / NCQ with ata
I am wondering what is the file system that
opensolaris 2009.6 creates for its installation, is
it zfs or ufs?
zfs
--
This message posted from opensolaris.org
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org
I don't know why but I
expected that the release build to be available in
the Mercurial repository after it gets released.
$ hg clone -r b111b ssh://anon at hg dot opensolaris dot org/hg/onnv/onnv-gate
abort: unknown revision 'b111b'!
So no, you cannot build previous releases of the
I have a x4150 running 5.11:
5.11 snv_85 i86pc i386 i86pc
After upgrading the SP FW, I wasn't able to boot it up.
After the grub menu was displayed it complained:
krtld: failed to open
krtld: bind_primary(): no relocation information found for module
/platform/i86pc/kernel/amd64/unix
After a while I was able to grab the screen immediately before the reboot and
the following is its content:
/kernel/misc/pci_autoconfig: undefined symbole 'class_pci_items'
/kernel/misc/pci_autoconfig: undefined symbole 'class_pci'
/kernel/misc/pci_autoconfig: undefined symbole
use mrxvt application. So, the problem is not with terminal application
on OpenSolaris, it doesn't run X at all (yet), but with OpenSolaris'
man, vi and other curses/termcap/you_know_better applications. To me it
looks like problem with curses/termcap capabilities. It works fine with
OpenSolaris does not have an rxvt terminfo entry
% ls -l /usr/share/lib/terminfo/r/rxvt
/usr/share/lib/terminfo/r/rxvt: No such file or directory
Seem this is bug 6839489:
http://bugs.opensolaris.org/bugdatabase/view_bug.do?bug_id=6839489
An ncurses rxvt terminfo entry exists in
| No I meant a 64bit version of OpenSolaris. Right
now it's only available in 64bit for SPARC if I'm not
mistaken.
Solaris has been a mixed 32/64bit install for many years.
The installer runs 32bit.
This has changed in OpenSolaris.
The OpenSolaris x86 installer / livecd runs the 64-bit
I could use some help in making my SIL-680 board work
under eon (or Opensolaris in general).
Does the card have a raid-mode jumper?
I think raid mode needs to be disabled.
Or is there a non-raid-mode firmware
available for the card?
Otherwise I think that a non-raid-mode
SIL-680 board should
CC-ed to xwinow-discuss, thread started at
http://www.opensolaris.org/jive/thread.jspa?threadID=125150tstart=0
Do you find the following error message in /var/log/Xorg.0.log ?
intel_bufmgr_fake.c:392: Error waiting for fence: Device busy.
No. I find in Xorg.0.log :
[...]
Error in
if i do truss -p 630 (Xorg process) i get and endless repetition of:
/1: setcontext(0xFD7FFFDFEB60)
/1: Received signal #14, SIGALRM, in ioctl() [caught]
/1: ioctl(14, 0x46445, 0xFD7FFFDFF3FC) Err#4 EINTR
/1: lwp_sigmask(SIG_SETMASK, 0x2000, 0x) =
I ran pkg install with truss, in the hope of
discovering why it takes so long to complete,
especially AFTER it has reported that every thing is installed.
You are running a fresh install of b133, correct?
Has pkg been always that slow?
I suspect that pkg has been reasonably fast for the
# tail pkg.log
1.7255 schedctl() = 0xFEC69000
0.0002sigaction(SIGINT, 0x08047650, 0x080476D0) = 0
421.4744 open(/usr/lib/locale/en_US.UTF-8/LC_MESSAGES/messages.mo,
O_RDONLY) Err#2 ENOENT
stack backtrace for the pkg process at
I suspect that pkg has been reasonably fast for the
first few packages that you installed, but has
become slower and slower the more packages
have been installed?
Not that much packages installed after fress install
That is, on your fresh b133 install from livecd, the
first package
BTW when did pkg switch to python 2.6 ?
It has been using python 2.6 for several builds now.
I have an old b129 installation and that is using
python 2.6 for /usr/bin/pkg.
--
This message posted from opensolaris.org
___
opensolaris-discuss mailing
Has pkg been always that slow?
I suspect that pkg has been reasonably fast for the
first few packages that you installed, but has
become slower and slower the more packages
have been installed?
Hello Mr. Keil: If you suspect a standard bin/pkg to run ^reasonably
fast ^, then all
As a matter of fact I had also thunderbird+firefox so the memory usage
was a bit high. I just retried it now without any other heavy app
other than X+gnome, and it went much much faster (7-8mn)
Since b132 there is a java vm process running on the gnome desktop.
It displays an icon in the
I lost my snapshots on swap now. do I need them ?
No, snapshots on a swap zvol are just a waste of disk space.
--
This message posted from opensolaris.org
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org
I thought it was a problem with the graphics driver, but you are right
as soon as I start gdm the box dies and my remote ssh session are dead..
What graphics hardware is that?
Intel video? Could be 6914386, which is not yet fixed in b133
I've noticed that since b132 my laptop freezes under
load. Just dies without any message other than
memory pressure, tcp defensive mode on.
Probably short of memory. I've _only_ 1GB which used
to be quite ok for a laptop.
AFAIK, the warning message is wrong. Although all
memory is in use,
Same here with me - thought that it may be some
problem in the versions since 128a - but it happens
more often. with 133 not as often as with 132 but
yesterday 2 times.
Thinkpad T61p with 4GB RAM - Virtualbox with win64 running .
Do you always get the freezes when virtualbox was
it freezes during the Creating plan when running pkg image-update,
either from b131 be or b132 (I kept both).
it freezes during the evaluating SUNWgcc package
when trying to ugrade from gui
I know the memory pressure msg is not directly related, but I can see
the memory being eaten up
Tried once again, it seems to freeze each time when
there is about 4K ram left.
Is that a 32- or a 64-bit system?
I do have 4G swap, almost not used at all.
Hmm, that is unexpected. How did you watch
swap space usage? swap -l ?
I just tried to pkg image-update a 64-bit b132 vbox
A few data points, for those who are about to do
this. On a single-CPU 2GB system I get:
PID USERNAME NLWP PRI NICE SIZE RES STATE TIMECPU COMMAND
37 root1 600 1231M 1131M sleep6:10 1.36% pkg
This system had lots of extra ips packages installed on top of
the
That is not good..Won't the machine just page to
compensate, though?
That's what I've been observing, with a 1GB virtualbox guest
and pkg image-update. It pages and is slow, but doesn't freeze.
But in my experiment the pkg process size is ~ 650 - 700 mbyte.
--
This message posted from
What other drivers are currently not distributed with OpenSolaris?
E.g. Adaptec *adp* drivers are missing in OpenSolaris
http://defect.opensolaris.org/bz/show_bug.cgi?id=112
http://defect.opensolaris.org/bz/show_bug.cgi?id=7976
I think there was the idea to make them available via the
extra
Sry I didn't found the right place for this, but I
wanted to inform you about 3 problems with this
forum:
Try the website-discuss list / forum
http://www.opensolaris.org/jive/forum.jspa?forumID=29
--
This message posted from opensolaris.org
___
Robert Milkowski wrote:
On 03/02/2010 12:25, Jürgen Keil wrote:
Robert Milkowski wrote:
Toshiba R600, up-to snv_129 X is working fine.
snv_131 and the moment Xorg starts the notebook does hard-reset (quick
power-off) - no crash dump, no nothing, When I booted under kernel
debugger
have 64bit system running on computer with 8gb RAM.
immediately after start ::memstat (mdb -k) shows
1164MB of Kernel, but after 2 or 3 days of idle
this number increased to ~2500MB. is it Ok or
something wrong?
Should be ok.
Could be cron jobs running during the night that
looks at lot of
Don't know if this is related,
Probably not, unless it hangs before displaying the
SunOS copyright banner of the kernel.
but I too have slow boot time for my Acer
7720G notebook and build 131.
Though I don't see 4 minute boot up time, it is more
like 2+ minutes to GDM.
There is a RFE
The stack matches that in 6914386 which is possibly a duplicate of
6911372 which is fixed in snv_131. This was introduced in b130, so it
fits your problem.
My suggestion would be to jump back to b129 (or whatever was your last
stable one) and upgrade to b131 which is currently available.
Robert Milkowski wrote:
Toshiba R600, up-to snv_129 X is working fine.
snv_131 and the moment Xorg starts the notebook does hard-reset (quick
power-off) - no crash dump, no nothing, When I booted under kernel
debugger the box just hangs and I can't go into the debugger.
I tried to boot
online 20:00:10 svc:/application/desktop-cache/icon-cache:default
online 20:01:08 svc:/system/hal:default
...
Note that between icon-cache:default and hal:default
there is an almost 60-second gap, I didn't find other
gaps like this in the whole svcs -a output.
Is there a
The stack matches that in 6914386 which is possibly a duplicate of
6911372 which is fixed in snv_131. This was introduced in b130, so it
fits your problem.
My suggestion would be to jump back to b129 (or whatever was your last
stable one) and upgrade to b131 which is currently
I have been finding my system taking a long time to
boot. In the order of 5 to 8 minutes. Part of it is
the zpools I have.
Which version of opensolaris are you using?
Are there lots of snapshots on the zpools?
However booting in text mode it
takes a long time to get any text on the screen.
Which version of opensolaris are you using?
It is a clean install of b131 (the issue occurred in
all of the b12x series also iirc)
Are there lots of snapshots on the zpools?
No, only 4 or 5 on my rpool.
Ok, so it isn't the problem with zpool import
running for a long time when *lots* of
So the main issue is:
After selecting an entry in grub to boot from, and
before the SunOS Release 5.11 Version ... copyright
banner appears there is a flashing _ for ~4-5
minutes.
Is there anyway to get text or any logging/tracing in
this time?
Did you try the verbose grub command?
Interestingly with grub in verbose the system waits
at the findroot line.
Seems to be stuck in the BIOS when trying to read
from one or more of the 16 HDDs connected to this
system.
Without the findroot line it brings up the SunOS
Release 5.11 Version ... copyright banner and ends
on the
So I have lots of files with weird characters in the
name. Those F6, F4, etc characters are listed as
?, for instance Making?Food?Recipe.doc. The
version of CIFS I use, (b125) does not allow listing
of files with those characters in WinXP clients. I
must stay with b125 because of issues in
However, I found that Xorg memory usage is still very high :
1446 root 448M 150M sleep 450 0:04:53 4.4% Xorg/3
especially compared to the one on my home server,
with basically the same session apps running
(including compiz, awn and conky) :
720 root 88M 58M sleep
while in my laptop I have an onboard intel :
PCI:*(0:0:2:0) 8086:27a2:1028:01c2 Intel Corporation Mobile 945GM/GMS,
943/940GML Express Integrated Graphics Controller rev 3, Mem @
0xeff0/524288, 0xd000/268435456, 0xefec/262144, I/O @
0xeff8/8, BIOS @ 0x/65536
...
For instance, i have a script which i use to check if
rsync is running, if it isn't running, then it will
rsync, if it is, then it should skip rsync. I put
this in crontab for every 15 minutes.
On FreeBSD this works fine, on OpenSolaris it doesn't
seem to be working.
any idea why this
I'm very puzzled by the memory usage in recent builds of osol-dev.
Yep.
E.g. on my b129 box a gnome-terminal process
is using 68 (!) shared libraries
% pldd `pgrep -x gnome-terminal` | wc -l
68
And I see lots of virtual memory used for mapping
the various font / icon-theme / mime
PID USERNAME SIZE RSS STATE PRI NICE TIME CPU PROCESS/NLWP
...
2749 bruno 195M 136M sleep 590 0:00:04 0.0% gconfd-2/1
The memory usage of that gconfd-2 process is very high.
On my opensolaris b131 system gconfd-2 consumes
13M memory, with a RSS of 7MB.
For some
Yes In deed I run compiz, though the normal
variant, mostly to be able to run avant-window.
It seems too be the bug you refer to.
If you have compiz enabled, logout from gnome
desktop and start a new session, is the gconfd-2
process size still that large?
--
This message posted from
E.g. on my b129 box a gnome-terminal process
is using 68 (!) shared libraries
% pldd `pgrep -x gnome-terminal` | wc -l
68
On opensolaris b131, this has increased to 76
shared libraries.
% pmap -x `pgrep -x gnome-terminal` | grep cache | wc -l
55
b131: 71 cache files
pmap -x
Thanks for the response. Here are the files as
requested.
When I run Install Solaris from the desktop there are
no drive or partition selections so I can't complete
the install. I have a 200GB Seagate drive attached to
the onboard SATA controller.
And that's apparently a VIA chipset SATA
2) WARNING: Mobile 4 Series chipset present, activating quirks Message
Seen at 124/128/129/130
Suggested work around is not usefull as it affects the use of Vbox.
3) Not powering off properly.
Seen at 124/128/129
When powered off/down , activity lights stay active.
4) suspend.resume
ugrading from SXCE b130 to osol-b131
Upgrading from SX:CE to OpenSolaris isn't possible,
did you reinstall OpenSolaris b131 from scratch?
the numbering of sata disks in ahci mode changed
Is this a (small) bug ?
Controller numbers shouldn't change by an upgrade.
But for a new install
After new install of b131, I get these messages :
ip: [ID 224711 kern.warning] WARNING: Memory pressure: TCP defensive mode on
Looks similar to these bugs:
http://bugs.opensolaris.org/bugdatabase/view_bug.do?bug_id=6910378
http://defect.opensolaris.org/bz/show_bug.cgi?id=14098
--
This message
Experiencing very strange behaviour with upgraded
OpenSolaris machine ( from snv_124 to snv_130 )
Machine gets panic, with the following error:
Just a wild guess...
An opensolaris upgrade currently has a nasty bug that
results in old kernel modules ending in the boot_archive:
Bug ID:
How am I suppose to figure out those numbers?
If fdisk can figure out the dimension, I suppose the
information format needed can be figured out
somehow?
Did you create a Solaris fdisk partition in the fdisk
utility? Is there a SunOS disk label written to the
Solaris fdisk partition?
I installed open solaris snv_111b on vmware esxi.
...
When i try to
boot opensoalris-1 from GNU GRUB Menu it dumps some
junk output and navigates back to GRUB Menu screen.
I think that is a known problem:
http://defect.opensolaris.org/bz/show_bug.cgi?id=6837
Or
last week, I decided to upgrade and got a OpenSolaris version
(osol-0906-x86.iso). Unfortunately, that was not what I expected:
it seems to be a SunOS 5.x kernel with GNU userland
(let's just say that I don't want GNU: GNU's not Unix).
Well, it does have both the gnu utilities (/usr/gnu/bin)
Ah, yup, it is. :(
Doesn't seem to work with lzjb either.
lzjb compression does work on a zfs root filesystem.
Note that the /rpool/boot/grub/* files are also read
during boot and must not be compressed with gzip
(lzjb is ok). There are no checks in the zfs code
that prevent the use of
I just received a kernel panic of a bug that is
assumably fixed:
Dec 15 19:09:30 iunis ^Mpanic[cpu1]/thread=ff01bdbc3180:
Dec 15 19:09:30 iunis genunix: [ID 335743 kern.notice] BAD TRAP: type=e (#pf
Page fault) rp=ff0008339c80 addr=8 occurred in module ip due to a NULL
pointer
... it bugs
me that sound has not been fix - it has
crackling/static sounds which were reported by many
member of the community.
Is that an audiohd device?
Build 129 has fixed this for me, see bug 12657 comment 2:
http://defect.opensolaris.org/bz/show_bug.cgi?id=12657#c2
--
This
There is no panic or syncing filesystems in
/var/adm/messages.
Is it possible to boot the server with kernel
option -k, disable the gui, and reproduce
the mkfile crash ? Does it reboot, or does it
enter the kernel debugger ?
--
This message posted from opensolaris.org
It shows my two USB sticks of the rpool being at
c8t0d0 and c11t0d0... !
How is this system even working?
I guess the physical device path for the usb sticks
has changed. But zfs boot is able to find the
correct devices, maybe using the disk's 'devid'
properties?
Or something strange (hw
I have that iso but can i use that to start an
installation of SXCE b127
No, I don't think so.
since I really don't like Linux b127
Sorry, I did forget that you didn't want to
use the opensolaris / indiana distribution...
or do I have to go the bootable usb route?
Booting the SX:CE
I get only information concerning the hard drive and
nothing about the optical drive.
I am using a Sony PCGA-DDRW3 Firewire optical drive,
Yep, I can reproduce it.
The problem is that the Solaris firewire drivers (hci1394
and friends) are not included in the SX:CE installer's
So far SXCE b127, b126, b123, b122, b121 have been
having this error ERROR: cannot find Java software,
Exiting to shell and the latest Solaris U8 does not.
I think this error is reported when the system was
unable to mount the install optical media...
What kind of optical driver are you
I am trying to get build 127 working on VMware but it
keeps panicking on boot. I have remembered to disable
the pcieb driver which got previous builds working,
but this build is not happy. It won't boot in either
32 or 64-bit mode. Is this a known bug and if so,
what is the bug number?
The
1 - 100 of 410 matches
Mail list logo
