Lcd not working on watchguard x700 with pfsense 2.0
-
Hope you might be able to add a little more info do i install lcdproc then follow your directions?
Just follow those instructions, don't install the LCDd package from inside pfSense. That .tar file will include everything necessary to run the Firebox's LCD just fine.
-
I get Read-only File System it seems for some reason it's not going to rw any ideas?
[2.0-BETA5][root@pfsense.local]/lib(14): ln -s libc.so.7 libc.so.6
ln: libc.so.6: Read-only file system
[2.0-BETA5][root@pfsense.local]/lib(15): ln -s libc.so.7 libc.so.6
ln: libc.so.6: Read-only file system
[2.0-BETA5][root@pfsense.local]/lib(16): /etc/rc.conf_mount_rw
[2.0-BETA5][root@pfsense.local]/lib(17): ln -s libc.so.7 libc.so.6
ln: libc.so.6: Read-only file system
[2.0-BETA5][root@pfsense.local]/lib(18): ln -s libkvm.so.5 libkvm.so.3
ln: libkvm.so.3: Read-only file system
[2.0-BETA5][root@pfsense.local]/lib(19): ln -s libkvm.so.5 libkvm.so.4
ln: libkvm.so.4: Read-only file system -
Hmm, that's odd. Looks like you're doing everything right.
I never tried it in beta5 though. What snapshot are you using? Perhaps try a different one.Steve
-
i'm using jan 16th right now
any suggestion as to one i should test?
-
I'm running Jan 13th in my X750E. No problems. I haven't installed the lcd package but I have used the mount RW script and it works.
Steve
-
I'm running Jan 13th in my X750E. No problems. I haven't installed the lcd package but I have used the mount RW script and it works.
Steve
It does work, but in my case I had to comment out the mount r/w and mount read only from the script as I am running a full install.
Perhaps that's what is happening to Jdetmold as well? -
If it's already a R/W filesystem then it shouldn't be giving read only errors no?
What's the result of running /etc/rc.conf_mount_rw on your system? (Assuming it's not production!)Steve
-
It does work, but in my case I had to comment out the mount r/w and mount read only from the script as I am running a full install.
Perhaps that's what is happening to Jdetmold as well?I am running the embedded image from cf so in all right I should need to change the file system to rw and this didnot work for me on the 13th build for some reason.
-
The odd thing for me is this. I did an upgrade from 1.2.3, then had to chose the reset to factory defaults option in the console, then import certain parts of my config.
The LCD is working for me though somehow.
Maybe that factory defaults option doesn't touch things installed via pkg_add? I always thought upgrading and reset defaults used an image to overwrite your disk.
-
The odd thing for me is this. I did an upgrade from 1.2.3, then had to chose the reset to factory defaults option in the console, then import certain parts of my config.
The LCD is working for me though somehow.
Maybe that factory defaults option doesn't touch things installed via pkg_add? I always thought upgrading and reset defaults used an image to overwrite your disk.
i can get the lcd to work if i upgrade from 1.2.3 it seems but not on a fresh install on 2.0
-
Hi,
Just picking up on the problems others have experienced with /etc/rc.conf_mount_rw not seeming to do anything. This is the point I am currently at.
After issuing /etc/rc.conf_mount_rw, it seems to accept the command. When issuing the command ln -s libc.so.7 libc.so.6, I get: "Read-only file system".
This is running from a CF card running: V2.0-BETA5 (i386) - built on Sun Jan 16 22:59:15 EST 2011.Did anyone find a solution to this?
-
Hi,
Just picking up on the problems others have experienced with /etc/rc.conf_mount_rw not seeming to do anything. This is the point I am currently at.
After issuing /etc/rc.conf_mount_rw, it seems to accept the command. When issuing the command ln -s libc.so.7 libc.so.6, I get: "Read-only file system".
This is running from a CF card running: V2.0-BETA5 (i386) - built on Sun Jan 16 22:59:15 EST 2011.Did anyone find a solution to this?
Not a good one. I build with 1.2.3 and update to a dec 3rd copy of embeded and that works. Have not found any other solutions.
It's strange because the gui is able to save settings
I should note if I do an upgrade to a current build it does not work
-
Ok, it seems that this is caused by the install script for the lcd package.
The script issues the following commands:
mount -u -w / Copy the stuff across and fix the permissions. mount -u -r /However that is now incompatible with the /etc/rc.conf_mount_rw command.
If you issue another 'mount -u -w /' you will then be able to enter enter the symlinks.
Then use /etc/rc.conf_mount_ro to remount the required parts read only again.
I assume that this is because of some change in the file system but I'm not BSD experienced enough to know. ::)Any comments from the development team?
I imagine this might also be what caused the boot problem.
Steve
Edit:
Yes this is definitely the case:[2.0-BETA5][root@pfSense.localdomain]/lib(48): mount -u -r / [2.0-BETA5][root@pfSense.localdomain]/lib(49): mount -p /dev/ufs/pfsense0 / ufs ro 1 1 devfs /dev devfs rw 0 0 /dev/md0 /tmp ufs rw 2 2 /dev/md1 /var ufs rw 2 2 /dev/ufs/cf /cf ufs rw 1 1 devfs /var/dhcpd/dev devfs rw 0 0 [2.0-BETA5][root@pfSense.localdomain]/lib(50): /etc/rc.conf_mount_rw [2.0-BETA5][root@pfSense.localdomain]/lib(51): mount -p /dev/ufs/pfsense0 / ufs ro 1 1 devfs /dev devfs rw 0 0 /dev/md0 /tmp ufs rw 2 2 /dev/md1 /var ufs rw 2 2 /dev/ufs/cf /cf ufs rw 1 1 devfs /var/dhcpd/dev devfs rw 0 0 [2.0-BETA5][root@pfSense.localdomain]/lib(52):This was NOT this case with Beta4.
-
Ok, it seems that this is caused by the install script for the lcd package.
The script issues the following commands:
mount -u -w / Copy the stuff across and fix the permissions. mount -u -r /However that is now incompatible with the /etc/rc.conf_mount_rw command.
If you issue another 'mount -u -w /' you will then be able to enter enter the symlinks.
Then use /etc/rc.conf_mount_ro to remount the required parts read only again.
I assume that this is because of some change in the file system but I'm not BSD experienced enough to know. ::)Any comments from the development team?
I imagine this might also be what caused the boot problem.
Steve
Edit:
Yes this is definitely the case:[2.0-BETA5][root@pfSense.localdomain]/lib(48): mount -u -r / [2.0-BETA5][root@pfSense.localdomain]/lib(49): mount -p /dev/ufs/pfsense0 / ufs ro 1 1 devfs /dev devfs rw 0 0 /dev/md0 /tmp ufs rw 2 2 /dev/md1 /var ufs rw 2 2 /dev/ufs/cf /cf ufs rw 1 1 devfs /var/dhcpd/dev devfs rw 0 0 [2.0-BETA5][root@pfSense.localdomain]/lib(50): /etc/rc.conf_mount_rw [2.0-BETA5][root@pfSense.localdomain]/lib(51): mount -p /dev/ufs/pfsense0 / ufs ro 1 1 devfs /dev devfs rw 0 0 /dev/md0 /tmp ufs rw 2 2 /dev/md1 /var ufs rw 2 2 /dev/ufs/cf /cf ufs rw 1 1 devfs /var/dhcpd/dev devfs rw 0 0 [2.0-BETA5][root@pfSense.localdomain]/lib(52):This was NOT this case with Beta4.
thats great! glad someone figured out the issue
although the boot issue stopping at "bootup complete" happens even if i dont install the lcd drivers
-
Unfortunately it appears more complicated than that.
It now seems that if you have run the script at all then the rc.conf_mount_rw/ro commands become ineffective. This will either leave your system permanently R/O or if you issue another 'mount -u -w /' then permanently R/W. One for the devs I think. I started a topic in 2.0 feedback.Steve
Edit: Too many threads with the same information.
See the main LCD thread for efforts to sort out this problem. Here.
