Re: [9fans] 9legacy Raspberry Pi HDMI video questions
I was able to remove the black border by appending the following lines to
config.txt:
hdmi_group=2
hdmi_mode=82
hdmi_cvt=1920 1080 60 3 0 0 1
framebuffer_width=1920
framebuffer_height=1080
max_framebuffer_width=1920
max_framebuffer_height=1080
The lesson I learned was that the Pi needs to be physically powered off after
making changes to the config file. ctrl-t ctrl-t r is not sufficient.
/
> On 5. Apr 2024, at 16.33, slash 9fans wrote:
>
> Dear 9fans,
>
> I am booting my Raspberry Pi 4B off the 9legacy SD card image
> (http://www.9legacy.org/download.html) and it boots fine with the default
> config.txt, but there is a 48-pixel wide black border on the screen.
>
> term% echo `{ dd -if /dev/screen -bs 64 -count 1}
> 0+1 records in
> 0+1 records out
> r5g6b5 0 0 1824 984
>
> The Pi is connected to a standard 1080p 60Hz monitor via HDMI. How can I get
> rid of the black border i.e. expand the screen size to 1920x1080? If anyone
> has accomplished this, could you share your config.txt? Also, how can I
> enable 24bit colors? Thank you.
>
> /
>
--
9fans: 9fans
Permalink:
https://9fans.topicbox.com/groups/9fans/T3b1609b3926a2f19-M9826399302cb5bf55ac94e01
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
[9fans] 9legacy Raspberry Pi HDMI video questions
Dear 9fans,
I am booting my Raspberry Pi 4B off the 9legacy SD card image
(http://www.9legacy.org/download.html) and it boots fine with the default
config.txt, but there is a 48-pixel wide black border on the screen.
term% echo `{ dd -if /dev/screen -bs 64 -count 1}
0+1 records in
0+1 records out
r5g6b5 0 0 1824 984
The Pi is connected to a standard 1080p 60Hz monitor via HDMI. How can I get
rid of the black border i.e. expand the screen size to 1920x1080? If anyone has
accomplished this, could you share your config.txt? Also, how can I enable
24bit colors? Thank you.
/
--
9fans: 9fans
Permalink:
https://9fans.topicbox.com/groups/9fans/T3b1609b3926a2f19-Maae5d0529903240b88db08b1
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
Re: [9fans] wildcard dns cname
Yes ping works and I can also make nslookups for hosts that don't match the wildcard. $ nslookup server.local Server: 10.0.0.1 Address: 10.0.0.1#53 Name: server.local Address: 10.0.0.1 $ nslookup other.local Server: 10.0.0.1 Address: 10.0.0.1#53 Name: other.local Address: 10.0.0.2 snoopy confirms that my server sees the expected packets on the right interface. Where is the problem? On Sun, Dec 4, 2011 at 2:21 PM, erik quanstrom quans...@quanstro.netwrote: cpu% ndb/dnsdebug @10.0.0.1 foobar 8300.2: sending to 10.0.0.1/10.0.0.1 foobar.local ip delay sure looks like your the dns packet is being dropped. you might want to check your routing. can you ping 10.0.0.1 from your linux host (with the interfaces dns is allowed to talk on). make sure you see those icmp packets on your plan 9 system before proceeding. - erik
Re: [9fans] wildcard dns cname
where is your soa record? /lib/ndb/local: dom=local soa= refresh=3600 ttl=3600 ns=server.local mb=em...@abcxyz.com
Re: [9fans] wildcard dns cname
ndb/dnsquery also fails for wildcard names but works for real ones: cpu% ndb/dnsquery f !dns: resource does not exist; negrcode 0 bar !dns: resource does not exist; negrcode 0 server server.local ip 10.0.0.1 other other.local ip 10.0.0.2 Why do dnsquery and dnsdebug give different results?
Re: [9fans] wildcard dns cname
ndb/dnsquery also fails for wildcard names but works for real ones: cpu% ndb/dnsquery f !dns: resource does not exist; negrcode 0 bar !dns: resource does not exist; negrcode 0 server server.local ip 10.0.0.1 other other.local ip 10.0.0.2 Why do dnsquery and dnsdebug give different results? For reference here is what dnsdebug gives me: cpu% ndb/dnsdebug fo any answer fo.local1 hrcame server.local bar any answer bar.local 1 hrcname server.local server any answer server.local 1 hrip 10.0.0.1 answer server.local 1 hrcname server.local other any answer other.local 1 hrip 10.0.0.2 answer other.local 1 hrcname server.local
Re: [9fans] New disk, i/o error
How did you used disk/prep? I ran 'disk/prep -bw -a^(9fat nvram fossil swap) /dev/sdE1/plan9'. When I ran it, my old disk was sdE0 and the new was sdE1. Now I notice the layout prep created is identical on both disks! su# disk/prep /dev/sdE0/plan9 # old 9fat0 204800 (204800 sectors, 100.00 MB) nvram 204800 204801 (1 sectors, 512 B ) fossil 204801 389668226(389463425 sectors, 185.71 GB) swap389668226 390716802(1048576 sectors, 512.00 MB) q su# disk/prep /dev/sdE1/plan9 # new 9fat 0 204800(204800 sectors, 100.00 MB) nvram 204800 204801(1 sectors, 512 B ) fossil 204801 389668226 (389463425 sectors, 185.71 GB) swap 389668226 390716802 (1048576 sectors, 512.00 MB) empty390716802 3907024002(3516307200 sectors, 1.63 TB) q I don't believe you can, fossil is usually used with venti and venti can definitely be grown on the fly, fossil alone is normally confined to just laptops where this is not an issue. Will this work: 1. boot off the old disk (/dev/sdE0/plan9) 2. disk/prep /dev/sdE1/plan9 - delete swap and fossil - create a new fossil at the same offset as the old one but bigger - write changes 3. mount /dev/sdE1/fossil I am trying to find a way to resize /dev/sdE1/fossil without losing the existing data on it.
Re: [9fans] ext2srv understands only 7bit ASCII file names?
unicode codepoints (runes) are abstract. we need to deal with encodings. the encoding utf-8 uses is not a single byte for anything above 0x7f. so essentially the encoding phase would be name[i] = (uchar)r. the decoding phase would be r = (Rune)name[i]. Thank you. I modified trfs.c and wrote trfs.latin1 which does this. Now I can do: disk/partfs /dev/sdU7.0/data disk/fdisk -p /dev/sdXX/data /dev/sdXX/ctl ext2srv -r -f /dev/sdXX/linux trfs.latin1 /srv/ext2 mount /srv/trfs /n/ext2 cd /n/ext2 dircp . $home and get no errors.
[9fans] New disk, i/o error
I began consolidating files with great joy from external ext2 disks to the new 2 TB fossil drive using trfs.latin1. After only 300 or so gigabytes I saw this on the console: fossil: diskWriteRaw failed: /dev/sdE0/fossil: score 0x016d1415: data Sun Oct 16 09:37:58 EDT 2011 part=data block 23925781: i/o error I searched through the 9fans archives and tried the following: - pulled the latest 9pccpuf from ftp.quanstro.net and booted with it. Made no difference. - ran 'echo debug sdE /dev/sdctl' and 'dd -if /dev/sdE0/data -of /dev/null -bs 8192'. No errors. Whenever I see this diskWriteRaw message on the console, file operations get stuck. fshalt jams too. This is fossil only. No venti. Now I am at a point where I get this error almost immediately after bootup. BIOS is (and has always been) set to AHCI mode with S.M.A.R.T. enabled. Brand new disk. Luckily I have all the data on the other drives. What to do next?
Re: [9fans] New disk, i/o error
i've also had trouble with usb disks. The errors come from sdE0 which is connected to sata port on the motherboard. Even when there are no usb disks attached at all. su# cat /dev/sdE0/ctl inquiry Hitachi HDS5C3020ALA632 model Hitachi HDS5C3020ALA632 serial ML0220FL0220F313JE2D firm ML6OA580 wwn 5000cca369cfb243 flag lba llba smart power nop ata8 sct udma 6 reg task 50 cmd 4c017 serr 0 ci 0 is 0 sig 101 sstatus 123 cmd hpcp cr fr pod sud st mode auto sataii geometry 3907029168 512 part data 0 3907029168 part plan9 63 3907024065 part 9fat 63 204863 part nvram 204863 204864 part fossil 204864 3905975489 part swap 3905975489 3907024065 I am beginning to think my new disk has bad sectors. Looking at the reviews on the internet I wouldn't be the first one. Is there a way to tell for sure? Or could it be the usb transfers corrupted my fossil and I need to check it? Can I do this while booting off it?
Re: [9fans] New disk, i/o error
dd -if /dev/sdE0/fossil -of /dev/null -bs 512k # or whatever partition. No errors, but I noticed it stopped just before 200 gigabytes. The total size of the plan9 partition is 1.81 terabytes. A related question: how should I interpret /dev/sdE0/fossil file size? # ls -l /dev/sdE0/fossil --rw-r- S 0 bootes bootes 199405273600 Sep 5 18:35 /dev/sdE0/fossil Yet: # con -l /srv/fscons prompt: df main: 196,000,014,336 used + 1,800,341,831,680 free = 1,996,341,846,016 (9% used) su# disk/fdisk /dev/sdE0/data cylinder = 8225280 bytes * p1 0 243201(243201 cylinders, 1.81 TB) PLAN9 Why such mismatch? And could this be related to the write errors?
Re: [9fans] New disk, i/o error
No errors, but I noticed it stopped just before 200 gigabytes. I kept reading the disk and got several read errors. Here is the first one: fossil: diskReadRaw failed: /dev/sdE0/fossil: score 0x016d1389: part=data block 23925641: eof reading disk Bad sector or something else?
Re: [9fans] New disk, i/o error
to me that looks like a mismatch between fossil's expectations for the partition and that actual partition size. i think you're just reading past the end of the partition. Indeed! su# disk/prep /dev/sdE0/plan9 9fat 0 204800(204800 sectors, 100.00 MB) nvram 204800 204801(1 sectors, 512 B ) fossil 204801 389668226 (389463425 sectors, 185.71 GB) swap 389668226 390716802 (1048576 sectors, 512.00 MB) empty390716802 3907024002(3516307200 sectors, 1.63 TB) Can I grow fossil on the fly? Why did prep create a 512MB swap partition when I have 2GB RAM?
[9fans] ext2srv understands only 7bit ASCII file names?
I have some files on an external ext2 drive that have whitespace and umlauts (ä, ö) in them. trfs took care of the whitespace. But ext2srv presents umlauts as a question mark symbol (�) and won't let me access the file (error: file does not exist). Where is the problem? These files show correctly in linux. As a workaround I can certainly boot that other OS and rename the files. It's just every time I see that penguin I get a rash.
Re: [9fans] ext2srv understands only 7bit ASCII file names?
if you know what the charset on disk is, you could probablly hack ext2fs into translating names. or (less hacky) you could write a transliterating fs, or add this to trfs' duties. Thank you. So now I know ext2srv is not doing any file name conversion. Good. Say I wanted to add the following capability to trfs: convert latin-1 ä and ö into their utf equivalents. I guess I would just follow the example of whitespace handling etc in trfs.c and recompile. Now, where is the latin-1 code table again...
Re: [9fans] ext2srv understands only 7bit ASCII file names?
latin-1 bytes 00-FF turn into unicode runes 00-FF. Then why doesn't it Just Work? Now I am confused (again).
Re: [9fans] copying fossil filesystem to a bigger disk
fossil/conf /dev/sdE0/fossil fossil.conf fossil/conf -w /dev/sdE0/fossil fossil.conf This was exactly what I needed. Thank you! My migration from old to new drive is now complete.
Re: [9fans] copying fossil filesystem to a bigger disk
you're not the first person to make this mistake, so i should have remembered this problem. sorry. Please don't apologize. You are the one guiding the blind. you need to mount both new and old afresh in /n/ and copy using your destination as /n/new and source as /n/old. using / as your source doesn't work because you have many things other than the file server intended mounted. for example, your first error messages are because #c is mounted on /dev. Aha! Maybe I finally got it. At least no errors: su# con -l /srv/fscons prompt: fsys new config /dev/sdE1/fossil fsys new config /dev/sdE1/fossil prompt: fsys new open -AWVP fsys new open -AWVP q su# mount /srv/boot /n/old main su# mount /srv/boot /n/new new su# disk/mkfs -s /n/old -d /n/new -U -r file system made su# con -l /srv/fscons prompt: fsys new sync fsys new sync new sync: wrote 0 blocks prompt: fsys new halt fsys new halt q Now let's see if it boots.
Re: [9fans] copying fossil filesystem to a bigger disk
snarf-paste error. the command was:
su# disk/mkfs -s /n/old -d /n/new -U -r {echo +}
Re: [9fans] copying fossil filesystem to a bigger disk
Now let's see if it boots. Almost there. I took out the old drive and made the new one sdE0. It started booting, until: fossil(#S/sdE0/fossil)... fsOpen: can't find /dev/sdE1/fossil ... panic Does fossil store the device name somewhere on the disk? (The drive was sdE1 when I formatted it.) How can I change it to sdE0?
Re: [9fans] copying fossil filesystem to a bigger disk
that's a good question. if you just want to copy everything, i use the shell
idiom
disk/mkfs {echo +}
I ran this in /usr/bootes/ as bootes:
su# disk/mkfs -a -s / {echo +} arch
processing /fd/7
mkfs: /fd/7:1: can't open //dev/consctl: '//dev/consctl' permission denied
mkfs: /fd/7:1: can't open //dev/kprint: '//dev/kprint' device or
object already in use
I guess it wasn't the brightest idea, because the arch file grew much
bigger than all my files put together on the old drive.
Should I mount the new drive to /n/kfs and not use the -a option? I
was a little confused about these references to kfs while my
filesystem is fossil.
Re: [9fans] copying fossil filesystem to a bigger disk
i think disk/mkfs is nearly idea for this, and isn't very dangerous. since your new fossil will start empty, you can't overwrite anything in the old fs. How do I generate the proto file? Do I have to go through an archive? Thank you for your patience.
Re: [9fans] copying fossil filesystem to a bigger disk
On Thu, Oct 6, 2011 at 3:35 AM, Peter A. Cejchan tyap...@gmail.com wrote: i use WD Caviar Green model WD20EARS (2TB SATA II) without any problems. I installed from erik's 9atom.iso Did you toggle any jumpers on the drive? I finally gave up and returned it. A new day, a new disk (with 512 byte sectors). I installed mbr, partitioned the disk, prepped the plan9 partition and formatted fossil on the new drive. Here's how my old and new disks look. su# cat /dev/sdE0/ctl # old inquiry SAMSUNG SP2004C model SAMSUNG SP2004C serial S07GJ10Y522190 firmVM100-32 wwn 5f0015522190 flaglba llba smart nop udma6 reg task 50 cmd 4c017 serr 0 ci 0 is 0 sig 101 sstatus 123 cmd hpcp cr fr pod sud st modeauto sataii geometry 390721968 512 part data 0 390721968 part plan9 63 390716865 part 9fat 63 204863 part nvram 204863 204864 part fossil 204864 389668289 part swap 389668289 390716865 su# cat /dev/sdE1/ctl # new inquiry Hitachi HDS5C3020ALA632 model Hitachi HDS5C3020ALA632 serial ML0220FL0220F313JE2D firmML6OA580 wwn 5000cca369cfb243 flaglba llba smart power nop ata8 sct udma6 reg task 50 cmd 4c017 serr 0 ci 0 is 0 sig 101 sstatus 123 cmd hpcp cr fr pod sud st modeauto sataii geometry 3907029168 512 part data 0 3907029168 part plan9 63 3907024065 part 9fat 63 204863 part nvram 204863 204864 part fossil 204864 3905975489 part swap 3905975489 3907024065 su# fossil/conf /dev/sdE0/fossil # old fsys main config /dev/sdE0/fossil fsys main open -V -c 3000 su# fossil/conf /dev/sdE1/fossil # new fsys main config /dev/sdE1/fossil fsys main open -V -c 3000 I would like to copy 9fat, nvram and fossil from the old drive to the new drive. 9fat is no problem. But how about nvram? Can I just use dd? As for fossil, I have not been able to figure out how to do this. replica(1) looks like has the capability to do this, but I don't want to experiment with my live data. Someone who knows how to do this, please advise. Also, do I need to run any additional fossil commands? The goal is to retire the old disk and boot off the new one with the only difference being that there is more free space now.
Re: [9fans] copying fossil filesystem to a bigger disk
the way to interpret this information is you may use 512 byte sectors if you really want to suffer terrible performance (usually 1/3 the normal performance for reasonablly random workloads.) That doesn't sound tempting at all. I am still within Amazon's return window. Can anyone recommend a 2 TB SATA drive that works on our favorite operating system out of the box at full speed? If it's quiet and cheap, all the better. let me think a bit about the correct solutions to this. it's clear to me that we just can't assume 512-byte sectors any more. I knew Plan 9 is picky about hardware, but a hard disk? *sigh*
Re: [9fans] copying fossil filesystem to a bigger disk
if you (slash) could just grab the atazz binary (ftp://ftp.quanstro.net/other/8.atazz) and send me the output of echo 'identify device' | 8.atazz -r [2=] /dev/sdE0 /tmp/somefile that would be great. thanks! Here you go. Again, sdE0 is the old drive, sdE1 is the new one. slash sdE0.out Description: Binary data sdE1.out Description: Binary data
Re: [9fans] copying fossil filesystem to a bigger disk
echo 'identify device' | 8.atazz -r /dev/sdE0 /tmp/somefile would be better Here goes. sdE0.out Description: Binary data sdE1.out Description: Binary data
Re: [9fans] copying fossil filesystem to a bigger disk
Do you use Fossil with or without Venti? There is many way to do it. Without Venti, you could use replica(1) to copy your file system from the old Fossil to the new Fossil. Fossil without Venti. Work has kept me busy but now I finally managed to attach the new drive to the system. Plan9 sees it as sdE1. The old drive is sdE0. (Booting off sdE0. This server does not have a CDROM drive.) old drive: su# cat /dev/sdE0/ctl inquiry SAMSUNG SP2004C model SAMSUNG SP2004C serial S07GJ10Y522190 firmVM100-32 wwn 5f0015522190 flaglba llba smart nop udma6 reg task 50 cmd 4c017 serr 0 ci 0 is 0 sig 101 sstatus 123 cmd hpcp cr fr pod sud st modeauto sataii geometry 390721968 512 part data 0 390721968 part plan9 63 390716865 part 9fat 63 204863 part nvram 204863 204864 part fossil 204864 389668289 part swap 389668289 390716865 new drive: su# cat /dev/sdE1/ctl inquiry WDC WD20EARS-00MVWB0 model WDC WD20EARS-00MVWB0 serial WD-WCAD-WCAZA9957825 firm51.0AB51 wwn 50014ee2b0ed5bde flaglba llba smart nop ata8 sct udma6 reg task 50 cmd 4c017 serr 0 ci 0 is 0 sig 101 sstatus 123 cmd hpcp cr fr pod sud st modeauto sataii geometry 3907029168 4096 part data 0 3907029168 The new drive is completely blank. It has 4096 byte sector size, and disk/mbr fails. su# disk/mbr -m /386/mbr /dev/sdE1/data mbr: secsize 4096 invalid How to get around this? I don't want to install another OS just to get the MBR in...
[9fans] copying fossil filesystem to a bigger disk
I am about to upgrade the disk on my cpu/disk server to a bigger one, and I want to maintain all the data. What is the most elegant way to do this? The new disk is blank.
[9fans] ANSI/POSIX port of aux/vga - where to find?
The wiki says The Plan 9 updates page contains an ANSI/POSIX port of aux/vga that is useful only for dumping registers on various systems. I am having trouble finding this tool. Any pointers? slash
[9fans] 9atom boot error on Gigabyte GA-H55M-USB3 with Intel i3-540
Greetings all. Booting up 9atom.iso fails on my hardware. I downloaded the latest from the ftp site: -r--r--r-- 1 none none 298452992 May 30 09:57 9atom.iso $ shasum 9atom.iso 53f79e7e152be2d68f578cd86198807d06fdbd3a 9atom.iso The Plan 9 startup menu comes up fine. However after selecting root it crashes. Here is the last screenful of console output: ELCR: 0EE8 nomp LAPIC: fee0 e000 404 0 rtl8169: unknown mac 8168 2c00 sdata: blind probe 1f0 sdata: blind probe 170 #S/sdE: ahci ich port 0xe0001000: sss 1 ncs 31 coal 0 mport 5 led 1 clo 1 ems 1 #S/sdE: ich: sata-II with 6 ports size = 0002; loc = 0160*4 #S/sdF: ahci jmicron port 0xe0002000: sss 0 ncs 31 coal 0 mport 1 led 1 clo 1 ems 0 #S/sdF: jmicron: sata-II with 2 ports ehci: handoff: bios owned ehci: handoff: bios owned 3452M memory: 256M kernel data, 3195M user, 3820M swap usb/kb... root is from (il, tcp, local)[local!#S/sdC0/data]: kfs...version...time... init: starting /bin/rc sdE0: LLBA 390,721,968 sectors SAMSUNG SP2004C VM100-32 S07GJ10Y522190 [newdrive] panic: bad led type panic: bad led type dumpstack disabled cpu0: exiting The CDROM drive where I am booting is PATA primary master. The hard disk is connected to the first SATA port on the motherboard. Any insight would be greatly appreciated. slash
